Mailing List os2-wireless_users@2rosenthals.com Archived Message #1077

From: "Dave Saville" <os2-wireless_users@2rosenthals.com> Full Headers
Undecoded message
Subject: Re: [OS2Wireless]Odd routing with two NICs
Date: Mon, 14 Aug 2006 08:30:11 +0100 (BST)
To: "OS/2 Wireless Users Mailing List" <os2-wireless_users@2rosenthals.com>

On Sun, 13 Aug 2006 19:31:30 -0400, Lewis G Rosenthal wrote:

>On 08/09/06 04:03 am, Dave Saville thus wrote :
>
><snip>
>> Now my desktop is connected to both networks and has "ipgate on" Its IP's are
>> 81.187.184.98/255.255.255.248 and 192.168.0.2/255.255.255.0
>>
>> Once the laptop has booted and XWLAN done it's thing I get on the "unused" NIC
>> on the 81 net 192.168.200.250/255.255.255.0 and the wifi nic
>> 192.168.0.49/255.255.255.0
>>
>> netstat -r from desktop
>>
>>   destination             router                netmask     metric flags intrf
>> default                81.187.184.97          0.0.0.0           0  UGSP   lan1
>> 12.172.135.250         81.187.184.97          255.255.255.255   0  UGHW   lan1
>> 69.90.217.26           81.187.184.97          255.255.255.255   0  UGHW   lan1
>> 81.103.221.14          81.187.184.97          255.255.255.255   0 UGHW3   lan1
>> 81.187.81.187          81.187.184.97          255.255.255.255   0 UGHW3   lan1
>> 81.187.184.96          81.187.184.98          255.255.255.248   0    UC   lan1
>> 127.0.0.1              127.0.0.1              255.255.255.255   0    UH     lo
>> 192.168                192.168.0.2            255.255.255.0     0    UC   lan0
>> 195.249.183.204        81.187.184.97          255.255.255.255   0  UGHW   lan1
>>
>>
>> netstat -r from laptop
>>
>>   destination             router                netmask     metric flags intrf
>>
>> default                192.168.0.4            0.0.0.0           0   UGP   lan1
>> 81.187.184.98          192.168.0.4            255.255.255.255   0  UGHW   lan1
>> 81.187.184.103         192.168.0.4            255.255.255.255   0  UGHW   lan1
>> 127.0.0.1              127.0.0.1              255.255.255.255   0    UH     lo
>> 130.88.202.49          192.168.0.4            255.255.255.255   0 UGHW3   lan1
>> 192.168                192.168.0.49           255.255.255.0     0    UC   lan1
>> 192.168.200            192.168.200.250        255.255.255.0     0    UC   lan0
>> 192.168.201.255        192.168.0.4            255.255.255.255   0  UGHW   lan1
>>
>> Now the odd part. If I do something that requires file & print, for example a
>> directory list on a shared drive,  it uses the 81 net - and it works. Now the
>> wired 81 net will get initialised first on an 81 address at boot. Then XWLan
>> comes along reassigns the NIC to 192.168.200.250 and inits the wifif card.
>> *Then* I login to the LAN which gets the shares going. I can't see either why
>> it does what it is doing, nor, more importantly, *why* it actually works.
>>  
>Hi, Dave. You don't mention what IP is assigned to your desktop or which
>machine on your network is located at 192.168.0.4. It's probably
>something else on your LAN which is routing the traffic. As all
>192.168.0.0 traffic should be routed through lan1 at 192.168.0.49
>(including the 192.168.200.0 traffic), this is probably where your
>packets are flowing, getting bounced that direction from the IP bound to
>the Wi-Fi NIC.

Lewis, I did give the IPs and netmasks at the top of the post. 192.168.0.4 is a
Sparc which also has nics on both networks. The access point is on the 192
network so normally any traffic from that net that wants to go elsewhere would
go through the Sparc.

However, in the case I mention the *only* lights on the 81 net switch that are
blinking are the desktop and the laptop. If it were going via the Sparc I would
see three blinking.


--
Regards

Dave Saville


Subscribe: Feed, Digest, Index.
Unsubscribe
Mail to ListMaster