Solaris + Switches + VLANs = wtf?

[Jason Shaw]

I'd suggest hooking a different box up to that port with the basic routing
information to operate only on that VLAN and make certain that it can
communicate properly.  That will help to narrow down the scope of the issue
by removing the switch/VLAN config from the problem.

-jason

On Mon, Nov 8, 2010 at 3:33 PM, aaron d <instantkamera-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org> wrote:

> Actually, again looking closer, I see I could be mistaken here. that
> "gateway" being to local interfaces IP is actually just saying ("Im directly
> connected to this subnet via infterface blah"). This is the same as the '*'
> in linux routing tables for the gateway, I assume.
> I've never really looked at solaris routing tables, so I apologize.
>
> That being said, it all looks good. Perhaps some issues with the switch
> port/vlans?
>
> aaron
>
> On Mon, Nov 8, 2010 at 3:28 PM, aaron d <instantkamera-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org> wrote:
>
>> OK, now I am thoroughly confused.
>>
>> You stated in the first post that the IP of this box, on the
>> 172.xx.236.0/23, was 172.xx.237.21, not 236.21 (note that 6 != 7)
>>
>> So your "gateway" is wrong for that subnet:
>>
>> >> 172.XX.236.0         255.255.254.0   172.XX.236.21        bnx0    1500*
>>    0   1 U        0      0
>>
>> The gateway (third column) is the IP of that very HOST, on the
>> aforementioned subnet.
>>
>> bnx0: flags=1000803<UP,BROADCAST,MULTICAST,IPv4> mtu 1500 index 2
>>>         inet 172.XX.236.21 netmask fffffe00 broadcast 172.XX.237.255
>>>         ether 0:1c:c4:6a:bb:10
>>>
>>
>> This is wrong.
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gtalug.org/pipermail/legacy/attachments/20101108/3e1f4826/attachment.html>