https://bugzilla.novell.com/show_bug.cgi?id=393801
User casualprogrammer@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c31
--- Comment #31 from Casual J. Programmer
There is a new dhcpcd 3.x (code fork), that does not support all the old (dhcpcd 1.x) options.
This needs to be reflected in yast2 lan then also, i.e. checkbox removed.
There is no default route set. I think, I know why this happens. Because the ifup-dhcp script detected, that there are two interfaces using dhcp, it disabled setting of a default route on the second one and this is wlan0. The dhcp on eth0 does not provide any, right?
This also has been working as expected before, in addition I would expect the script to detect that eth0 is configured but no cable attached. As you can see by the following, a dhcpcd is started for each NIC as you said: # ifdown wlan0 wlan0 device: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) # ifdown eth0 eth0 device: Intel Corporation PRO/100 VE Network Connection (rev 02) # ifup eth0 eth0 device: Intel Corporation PRO/100 VE Network Connection (rev 02) Starting DHCP Client Daemon on eth0... . . . . . . . . . . . . . . . no IP address yet... backgrounding. # ifup wlan0 wlan0 device: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) wlan0 warning: WPA configured but may be unsupported wlan0 warning: by this device wlan0 starting wpa_supplicant WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported Starting DHCP Client Daemon on wlan0... . . . . . . . . . IP/Netmask: '192.168.0.40' / '255.255.255.0' And it also indicates the wlan0 gets an IP while eth0 gets none ( no wonder if no cable is present ) consequently: # ps ax | grep dhc 14118 pts/2 S 0:00 /sbin/dhcpcd -D -K -N -t 999999 -h workstation6l -c /etc/sysconfig/network/scripts/dhcpcd-hook eth0 14306 ? Ss 0:00 /sbin/dhcpcd -R -G -N -Y -t 999999 -h workstation6l -c /etc/sysconfig/network/scripts/dhcpcd-hook wlan0 14619 pts/2 R+ 0:00 grep dhc
This needs explicit configuration of the dhcp clients in ifcfg files;
Thanks that you point that out, I still contend that this should be done by the setup program ( yast2 lan ) in the first place. I am probably not the only one falling into that trap, and my ( as well as others ) in depth knowledge of networking is limited.
Zeroconf aka APIPA link local route (RFC 3927):
From my Windows XP Installation I am used to use multiple interfaces in
Thanks again for pointing out. Not sure if this is relevant for proper function, if it doesn't hurt it may well sit there. Again I expect the setup program to take care of that. In response to comment #29 Also very helpful information, thank you. Again if I set both NICs to be started at boot, I expect the setup scripts to detect that eth0 has no cable. For me it used to work as expected. When eth0 cable connected no need for wlan0, if cable not present wlan0 required parallel I can even add a modem connection and use it together with LAN and WLAN, the load gets split among all connected interfaces. Sounds reasonable for me. Somehow.. In any case, I am very grateful to you for taking the time to explain issues in depth. Thank you! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.