7 апреля 2016 г. 20:50:13 CEST, "Schweiss, Chip" пишет:
>On Thu, Apr 7, 2016 at 12:51 PM, Michael Talbott
>wrote:
>
>> Oh, I see. Sorry about that, reading it on my phone didn't render
>your
>> diagram properly ;)
>>
>> The reason this is happening is because the omnios box has knowledge
>of
>> b
I see. I know in the linux world, one could use iptables to tag packets coming
in on an interface and then route the response back out of the interface they
came in which would solve the issue (which I've done before to work around a
similar oddball issue), but, I have no idea if that sort of lo
On Thu, Apr 7, 2016 at 12:51 PM, Michael Talbott wrote:
> Oh, I see. Sorry about that, reading it on my phone didn't render your
> diagram properly ;)
>
> The reason this is happening is because the omnios box has knowledge of
> both subnets in its routing table and it always takes the shortest p
Oh, I see. Sorry about that, reading it on my phone didn't render your diagram
properly ;)
The reason this is happening is because the omnios box has knowledge of both
subnets in its routing table and it always takes the shortest path to reach an
ip destination.
So you will need to put the "cl
It sounds like you're using the same subnet for management and service traffic,
that would be the problem causing the split route. Give each vlan a unique
subnet and traffic should flow correctly.
Michael
Sent from my iPhone
> On Apr 7, 2016, at 8:52 AM, Schweiss, Chip wrote:
>
> On several o
On several of my OmniOS hosts I have a setup a management interface for SSH
access on an independent VLAN. There are service vlans attached to other
nics.
The problem I am having is that when on privileged machine on one of the
vlans also on the service side that has access to the management SSH
