WLAN/dhcp question - not updating resolv.conf, routing
Hi all, I just completed installing SuSE 8.1 on my laptop which has a 3Com xjack WLAN card installed. I downloaded the podlu driver and installed it and I am now getting an ip address via dhcp on the card - eth1 (eth0 is a built in 10/100 adapter). However, the resolv.conf file is not being updated nor am I getting a default gateway. If I manually add my nameserver entries to /etc/resolv.conf dns queries work correctly. However, if I add a gateway with "route add -net 0.0.0.0 netmask 255.255.255.0 gw 192.168.2.2" - which should be correct - I still cannot get off my local net onto the Internet. Anyone have any ideas why dhcp wouldn't be updating the network settings correctly? Seems odd that it will get an address but nothing else from the dhcp server (which is running on another SuSE 8.1 server and is serving addresses, nameservers, gateways, etc just fine to other machines - both SuSE and Windows.) thanks in advance! -- John LeMay KC2KTH Senior Enterprise Consultant NJMC | http://www.njmc.com | Phone 732-557-4848 Specializing in Microsoft and Unix based solutions
On Wed, Apr 02, 2003 at 11:44:46AM -0500, John LeMay wrote:
Hi all,
I just completed installing SuSE 8.1 on my laptop which has a 3Com xjack WLAN card installed. I downloaded the podlu driver and installed it and I am now getting an ip address via dhcp on the card - eth1 (eth0 is a built in 10/100 adapter). However, the resolv.conf file is not being updated nor am I getting a default gateway. If I manually add my nameserver entries to /etc/resolv.conf dns queries work correctly. However, if I add a gateway with "route add -net 0.0.0.0 netmask 255.255.255.0 gw 192.168.2.2" - which should be correct - I still cannot get off my local net onto the Internet.
Anyone have any ideas why dhcp wouldn't be updating the network settings correctly? Seems odd that it will get an address but nothing else from the dhcp server (which is running on another SuSE 8.1 server and is serving addresses, nameservers, gateways, etc just fine to other machines - both SuSE and Windows.)
Do you have onboard network network, in addition to the WLAN card? Then the onboard interface is typically configured for DHCP, and it is started first. The consequence is that the DHCP client running for the WLAN device is considered "secondary" and it won't modify resolv.conf, nor set a default route. Solution: Either append DHCLIENT_PRIMARY_DEVICE=yes to each ifcfg-* file that is configured for DHCP, or set DHCLIENT_PRIMARY_DEVICE=no for eth0, or don't start eth0. If you don't have onboard network, we'd need to look further. Peter
the onboard interface is typically configured for DHCP, and it is started first. The consequence is that the DHCP client running for the WLAN device is considered "secondary" and it won't modify resolv.conf, nor set a default route.
Bingo, this is exactly the case. I had pretty much pieced this together through my trials, but I certainly appreciate the reply verifying it.
Solution: Either append DHCLIENT_PRIMARY_DEVICE=yes to each ifcfg-* file that is configured for DHCP,
Ah, that's a decent soluion. Didn't know I could do that. I assume this will have both interfaces update routing and resolv.conf? I actually took to setting eth0 to STARTMODE="manual" since I rarely use the onboard nic. Thanks a lot for the reply!
participants (2)
-
John LeMay -
poeml＠cmdline.net