[Bug 393801] New: wlan ( ipw3945) access with ifup not working properly
https://bugzilla.novell.com/show_bug.cgi?id=393801 Summary: wlan ( ipw3945) access with ifup not working properly Product: openSUSE 11.0 Version: Factory Platform: x86 OS/Version: openSUSE 11.0 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: casualprogrammer@yahoo.com QAContact: qa@suse.de Found By: Beta-Customer After a clean network install & update from factory ( post Beta3 ) connection with NetworkManager (default installation setting) works as expected. Changing that to ifup with yast2 lan results in a configuration that needs several times ifdown / ifup / dhclient to finally connect. Please advise what kind of information you require. Notebook: Fujitsu Siemens Amilo Si 1520 Graphics: Fujitsu Siemens Mobile 945GM/GMS/GME, 943/940GML Express Monitor: QUANTADISPLAY LCD Monitor 1280x800@60Hz Wireless: Intel PRO/Wireless 3945ABG Network Connection Sound: 82801G (ICH7 Family) High Definition Audio Controller Desktop: gnome-desktop-2.22.1-21 YaST GUI: yast2-qt-2.16.49-2 OS: openSUSE 11.0 (i586) Beta3plus VERSION = 11.0 Kernel: 2.6.25.4-6-pae -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=393801
Andreas Jaeger
https://bugzilla.novell.com/show_bug.cgi?id=393801
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c1
Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=393801
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c2
Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=393801
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c3
--- Comment #3 from Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=393801
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c4
--- Comment #4 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=393801
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c5
Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=393801
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c6
--- Comment #6 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=393801
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c7
--- Comment #7 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=393801
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c8
--- Comment #8 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=393801
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c9
Marius Tomaschewski
Re comment #2 setting up static IP is not possible, yast2 lan hangs at "write routing configuration" and needs to be killed, see yast2logs attached.
After starting yast2 lan again it shows the static IP for WLAN, on closing hangs again. Probably a new Bug ?
It looks like. I've "cloned" the bug, so we can handle them separately... First of all, don't use the ISC dhclient for multiple parallel running interfaces - it is not supported by the network scripts (ifup-dhcp) until now. You should get this message in /var/log/messages: dhclient is already running for some interface. Stop it first. If you want to run dhcp on several interfaces, please use dhcpcd. [You can use it with STARTMODE="ifplugd" + different IFPLUGD_PRIORITY's for the interfaces (so only one is up).] You can change it in /etc/sysconfig/network/dhcp by setting: DHCLIENT_BIN="dhcpcd" or DHCLIENT_BIN=" Further, when you configure to use static IP, please make sure that there is: - one default route in /etc/sysconfig/network/routes (ifroute-*) default 192.168.0.1 0.0.0.0 wlan0 - a nameserver and a search entry in /etc/resolv.conf search ac nameserver 192.168.0.1 When you're using dhcp, make sure at least, there is no static default route in /etc/sysconfig/network/routes (ifroute-*). You're already in Cc of Bug #386364 that is about driver specific association problems. But you seem to not to have any? You write in comment #5 "Static IP seems to work, but not on boot." What exactly does this mean? Are there some error messages? What is the output of "rcnetwork restart -o boot debug"? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=393801
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c10
--- Comment #10 from Marius Tomaschewski
after updating from factory this morning the issue seems to be resolved, on boot internet access is established.
Hmm... And what happens now with your eth0 interface? Before, both was with BOOTPROTO=dhcp (before you've changed one to static): PRO/100 VE Network Connection PRO/Wireless 3945ABG Network Connection Are you using one of the interfaces with BOOTPROTO="static" now? Can you provide the network script logs from /var/log/boot.msg? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=393801
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c11
--- Comment #11 from Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=393801
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c12
--- Comment #12 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=393801
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c13
--- Comment #13 from Marius Tomaschewski
The most easy first: "You're already in Cc of Bug #386364 that is about driver specific association problems. But you seem to not to have any?"
No I don't have any driver related issues and I doubt there are any, as you may judge by comment #0 and comment #22 of that bug. If the driver had an issue, it would not be able to talk to the ap and associate. I rather think that bug needs to be set up afresh to make sure people talk about _identical_ issues and facts.
Yes, this is also my impression. But this is Helmut's issue :-)
For the rest you gave me a lot of reading, and I will work it off one by one. so be patient.
OK, thank you very much for all your efforts of bug hunting!!
One thing to think about though: Although I may be setting up networks in a nonstandard way with respect to using two interfaces in parallel, this used to work without problem in the past...
It still works using the dhcpcd client. Please give it a try too... It never worked in the past with ISC dhclient (dhcp-client package) or it was due to accident. The scripts never supported this. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=393801
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c14
--- Comment #14 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=393801
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c15
--- Comment #15 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=393801
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c16
--- Comment #16 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=393801
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c17
Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=393801
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c18
Marius Tomaschewski
I just had a chance to repeat all the steps for configuration, I will just list them here, then we can decide whether some of them are bugs in their own right.
Yes, I think we definitely have to handle them separately.
Clean installing from factory sets network up for use with NetworkManager, to use the traditional method yast2 lan needs to be invoked and NICs reconfigured.
First of all "Network Settings/Global Options" check "Traditional Method" with ifup, as well as set up the credentials for wlan ( ESSID / Pasphrase ) and the Routing Gateway.
Yast2 spends a lot of time setting up routing, it then comes to a point where it wants to install smpppd and kinternet, which fails as during network setup repos are not available as network is down.
Checking this shows wlan0 comes preconfigured with "Enable Device Control for Non-root User Via Kinternet" unchecking this makes yast2 lan finish properly.
Nothing goes at all..
there are two instances of dhcpcd running, killing and restarting one with dhcpcd wlan0 achieves nothing.
As wpa_supplicant is required, checking whether it's up. ps -A | grep wpa shows 2 instances are running. ifdown wlan0 makes one go away. So there must be one left over from NetworkManager. Killing it and ifup wlan0 produces a state where the AP (192.168.0.1) can be pinged but no network access possible.
Going over every step again, reveals that yast2 lan is removing the entry for the routing gateway when started, it has to be set explicitly again before closing it.
After that both dhcpcd as well as dhclient can get IP address and Name Resolution.
OK, cool.
One thing I added in the previous experiments was the concurrent use of dhcpd and dhclient, as I wasn't aware that they are really two different animals
Yes, it are different animals. Michal, as most of the steps was done in yast2, I reassign to you for an review and then you'll "bounce back" when the reason is in sysconfig, OK? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=393801
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c19
--- Comment #19 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=393801
User varkoly@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c20
Peter Varkoly
https://bugzilla.novell.com/show_bug.cgi?id=393801
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c21
Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=393801
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c22
Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=393801
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c24
--- Comment #24 from Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=393801
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c25
Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=393801
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c26
--- Comment #26 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=393801
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c27
--- Comment #27 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=393801
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c28
--- Comment #28 from Marius Tomaschewski
yes it is set to " -B", removing "-B" solves the issue.
It was set because I checked "Request Broadcast Response" under "DHCP Client Options" in yast2 lan's "Global Options".
Not sure why this should cause trouble, I always had this set and it worked as expected.
There is a new dhcpcd 3.x (code fork), that does not support all the old (dhcpcd 1.x) options. See also "man dhcpcd" and /usr/share/doc/packages/dhcpcd/dhcpcd-1-vs-3. The maintainer of dhcpcd has a fix (or is working on it) to remove all unsupported options when the package gets installed. (In reply to comment #26 from Casual J. Programmer)
Also I note, after having removed -B from DHCLIENT_ADDITIONAL_OPTIONS, setting up eth0 and selecting "Activate device: At Boot Time" still renders wlan0 nonfunctional. This is the case where AP can be pinged, yet no network connection.
# ping google.com connect: Network is unreachable
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? Can you provide the output of "ps ax | grep dhcpcd" please to verify? This needs explicit configuration of the dhcp clients in ifcfg files; please set: - in ifcfg-eth0: DHCLIENT_SET_DEFAULT_ROUTE="no" - in ifcfg-wlan0: DHCLIENT_SET_DEFAULT_ROUTE="yes" consider to set also: DHCLIENT_SET_HOSTNAME DHCLIENT_SET_DOMAINNAME DHCLIENT_KEEP_SEARCHLIST DHCLIENT_MODIFY_RESOLV_CONF DHCLIENT_MODIFY_NTP_CONF DHCLIENT_MODIFY_NIS_CONF
"Configured routes for interface wlan0: 169.254.0.0 - 255.255.0.0 wlan0"
is supposed to be ???
Zeroconf aka APIPA link local route (RFC 3927): "a host may automatically configure an interface with an IPv4 address within the 169.254/16 prefix that is valid for communication with other devices connected to the same physical (or logical) link." You can set the "-L" option in DHCLIENT_ADDITIONAL_OPTIONS globally or for interface, where you don't want it. See also "man dhcpcd" and also LINKLOCAL_INTERFACES in /etc/sysconfig/network/config. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=393801
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c29
--- Comment #29 from Marius Tomaschewski
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.
participants (1)
-
bugzilla_noreply@novell.com