Jaunty network problem

[Mark Williams]

Huisi Wang wrote:
>> Generally, buggy DHCP server. I often find external wifi does the
>> reverse of this.
>>
>> connect to wireless.
>>
>> type >route
>>
>> This tells you what the gateway _should_ be.
>>
>>  >cat /etc/resolv.conf might be handy in case it's name resolution that
>> didn't set up right.
>>
>> connect to eth0
>>
>> repeat the above steps.
>>
>> if it's route, >route add gw nn.nn.nn.nn (I think that's the right order :)
>>
>> if it's resolv.conf, edit it / replace it with the wireless version &
>> see if that works.
>>
> I have tried your instructions. I find that, when connected to eth0,
> there is 'default gateway'. But 'route' output is different to
> wireless one. See below:
> 
> wireless output:
> 
> 192.168.86.0    *               255.255.255.0   U     2      0        0 wlan0
> link-local      *               255.255.0.0     U     1000   0        0 wlan0
> default         192.168.86.7       0.0.0.0         UG    0      0        0 wlan0
> 
> wired output:
> 
> 192.168.86.0    *               255.255.255.0   U     1      0        0 eth0
> default         192.168.86.7       0.0.0.0         UG    0      0        0 eth0
> 
> There is no 'link-local' configuration in wired route output. Is it
> the problem? /etc/resolv.conf has the same configuration.
> 
> Thanks,
> Huisi
> 

Possibly yes; try adding it.

Mine (which works) is:
Destination     Gateway         Genmask         Flags Metric Ref    Use 
Iface
192.168.1.0     *               255.255.255.0   U     1      0        0 eth0
default         router          0.0.0.0         UG    0      0        0 eth0

man route is quite detailed.

Can you ping 192.168.86.7 from your eth0? If not check ifconfig, in 
particular the netmask I have seen differ from the route version - that 
doesn't work too well! ifconfig can set as well as show it.

Mark.