|
Bugzilla – Full Text Bug Listing |
|
Description
Winfried Dobbe
2006-03-21 17:29:28 UTC
Please attach /var/log/NetworkManager here. Looking at the now attached /var/log/messages from the same time span, I see the message: Device 'eth1' DHCP transaction took too long (>25s), stopping it. I think that was already changed for bug 153243. So I'll try again with those updated NetworkManager rpms when I'm in the office again tomorrow. Created attachment 74453 [details]
excerpt of /var/log/NetworkManager during same time as pasted /var/log/messages output
Tried with updated NetworkManager packages. No result. Attaching todays messages and NetworkManager log. Created attachment 74646 [details]
todays output in /var/log/NetworkManager
Created attachment 74650 [details]
todays output in /var/log/messages
The ip address you get is actually the autoip fallback (zeroconf/bonjour). Winfried: Is this with Timo's test packages? Timo: What did you bump the DHCP timeout to in these packages, if anything? The text still says 25s but it looks like it waited 40s ... hrm. Changing the bug subject, this has nothing to do with NIS or the lack thereof. How does this differ from Bug #153243? This is ipw2200 connecting to a broadcast, non-encrypted, access point, right? So while we successfully connect and associate, DHCP fails as if we are not speaking the same language. There are no other access control methods on this AP, right? No MAC filtering? The log looks fine. Assuming you have the wireless settings right, it looks like you just do not have a functioning DHCP server on the LAN. Hrm. (In reply to comment #8) > Timo: What did you bump the DHCP timeout to in these packages, if anything? > The text still says 25s but it looks like it waited 40s ... hrm. Hm, I bumped the timeout to 40s. Looks like I did not change the substring 25s in the nm_info() call, though. No worries. I just submitted to autobuild an NM with a DHCP timeout of 45s. Yes, sorry that I forgot to mention it's a WLAN without encryption. If I configure network device in Yast to "traditional with ifup", I get a valid ip address instantly. Winfried: Can you please try the latest NetworkManager packages (0.6.2)? Timo and I think ipw2x00 should work fine, now. Thank you! Thanks for the update. We are in the middle of an acceptance test, I hope I have time to test it tomorrow, else it will be Friday. One of the dependencies of the NetworkManager 0.6.2 is wpa_supplicant >= 0.4.8-9. In the factory directories I can see only the source rpm of wpa_supplicant 0.4.8-8. Can you add 0.4.8-9 ? Maybe the mirrors are not properly synced. Looks like gdwg.de is up to date. http://ftp.gwdg.de/pub/opensuse/distribution/SL-OSS-factory/inst-source/suse/i586/wpa_supplicant-0.4.8-9.i586.rpm I wish I could be more positive, but I wasn't able to connect to either our non-encrypted WLAN at work or my WPA/ascii/TKIP WLAN at home. The progress dialog continues until "57 % IP configuration started". For the WPA WLAN it keeps asking for the pasphrase then even though I enter the correct one. On the positive side: my router didn't crash anymore, despite many attempts to connect to it. Relevant output of /var/log/NetworkManager attached. Created attachment 75925 [details]
Trying to attach to wpa wlan with NetworkManager-0.6.2
Created attachment 75926 [details]
Trying to connect to unencrypted WLAN using NetworkManager-0.6.2
While waiting for the train last night I tried to connect to unencrypted WLAN that Dutch railway company offers nowaday. I got connected at first try. Don't know what's the difference, but I'll attach output in log file in case it is of any help. Created attachment 76026 [details]
Output in /var/log/NetworkManager of succesful connection with ipw2200
Winfried: With the latest packages, are you still seeing a problem on the other AP that did not work? With beta 9 and NetworkManager-* upgraded to 0.6.2-10, I still can't connect to my WPA WLAN. Actually the progress indicator never makes it past the "28% configuring device" stage. Log attached. ps: for next 2 weeks I'm on honeymoon, so I'm afraid that I can't test anymore before 10.1 release. Created attachment 78449 [details]
unsuccessfull attempt to connect to WPA wlan
Thanks for the information, Winfried. Enjoy your honeymoon!
Winfried: I hope that your homeymoon was wonderful!
Can I trouble you to retest and verify if your problem is fixed?
I built updated packages, and put them up for you:
http://primates.ximian.com/~rml/misc/NetworkManager/
Preferably, it would be nice if you had the latest SUSE build in general, too, in case a kernel or wpa_supplicant update helps out, too.
Please confirm success or provide new details of the problem. Thank you very, very much!
No problem. My HP laptop is in the office, where I'll be on Thursday and Friday. At the same time opensuse 10.1 should be released, so I'll let you know the result when I've installed that and the new networkmanager (probably Friday). Unfortunately, can't connect yet to either my WPA access point or unencrypted WLAN at work with network manager. I installed 10.1 final and added the rpms from the link you provided. When trying to connect to the WPA access point, network manager comes asking for the key every 15 seconds or so. Since there was only an updated rpm for networkmanager-gnome, I also tried with the Gnome desktop iso KDE but that gave same result. I will attach excerpt from /var/log/NetworkManager. Created attachment 83557 [details]
excerpt for /var/log/NetworkManager with Suse 10.1 final and NetworkManager 0.6.2-32
This should work fine with an ipw2200. Are you sure that your pairwise and group ciphers are TKIP? Can you retest, choosing "Automatic (default)" for "Type", please? Attached are screenshots of wlan AP settings and the network manager dialog. If I disable the WPA security on the AP I can connect to it with network manager, not when using WPA. But I couldn't connect to it with network card set to "traditional ifup" either when using WPA. AP still hangs from time to time when connecting from Suse, which it doesn't when I connect to WLAN from Windows. Created attachment 83827 [details]
settings of WLAN access point
Created attachment 83828 [details]
screenshot of network manager dialog
Never mind the WPA passkey, I have already changed it after this post.
Have you tried with nm-applet? Same result? Anyhow, if this also fails with ifup ... Same result. Maybe it's better to stop with this until I can test it with another WPA AP (mine is not exactly top quality). But then there is still the question why network manager doesn't want to connect to the unprotected WLAN at work. That one works ok with ifup. I agree. I will close this bug and leave you alone ;) but can you reopen a new bug if and when you retest with a new AP, and continue to see problems? |