This is a discussion on name service not correctly set using wlan within the Linux Networking forums, part of the Linux Forums category; Dear all, i'm using a laptop running Suse8.1 with a custom compiled kernel 2.4.24 which is ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Dear all,
i'm using a laptop running Suse8.1 with a custom compiled kernel 2.4.24 which is connected either to a wired ethernet connection or to a wireless. Both interfaces were set-up using the standard Suse config tool Yast in the same way as far as name server and routing goes (letting DHCP do all the work). The wireless has of course some additonal settings. However, somewhere there seems to be a difference in the configuration, which I can't figure out (at least not from looking at the /etc/sysconfig/network/ifcfg-ethx files. When I reboot the laptop with the cable plugged in, the host name and DNS is apparently set up correctly. However, when I have only the wireless device activated, I see that the when detecting the wireless interface, it gets the correct IP address and hostname (wlan-xxx), however this information does not seem to propagate further than this. When the boot process is finished, the name of the machine is still linux2 (local name). I suppose, DHCP for the second interface (eth1) is called with different options than for the wired one (eth0). Were do I need to look for this, if not in ifcfg-eth0/1? Also, I noticed that also /etc/resolv.conf is not updated when the wlan interface starts, but it is when eth0 starts. Thanks for any help to point me in the right direction ... Cheers, Riko |