|
Bugzilla – Full Text Bug Listing |
| Summary: | NetworkManager unable to connect to WPA1 wireless network | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | David Canar <davidcanar> |
| Component: | Network | Assignee: | Timo Hoenig <thoenig> |
| Status: | VERIFIED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | aj |
| Version: | Beta 5 | ||
| Target Milestone: | Beta 7 | ||
| Hardware: | i686 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | 153536 | ||
| Bug Blocks: | |||
| Attachments: |
This is what shows on /var/log/messages
/var/log/NetworkManager log file of the operations described on Comment #7 this is what shows 'hwinfo --netcard' |
||
|
Description
David Canar
2006-02-27 13:48:58 UTC
Created attachment 70399 [details]
This is what shows on /var/log/messages
BTW using ifup works without problems > Hi, I'm using OpenSuSE 10.1 beta 3 but I have installed NetworkManager
> 0.5.1cvs20060221-2 and NetworkManager-kde 0.1r5748-2 on my Laptop HP ze2308wm
> with ndiswrapper 0.11 and I have problems trying (...)
Hello David. At first the distribution's name is still SUSE Linux, openSUSE is the project. Second: Are these packages the shipped versions for SUSE or are they third party? You should update to beta5 and try this again. If the problem still exists there, please reopen this bug. Beta3 is too outdated by now.
Sorry I installed Beta 3 but I've been updating all the packages using the "FACTORY" yast repository so ALL the packages I have must be from beta 5 or newer. I have installed the latest version of NetworkManager that is offered on the FACTORY repository so this is a problem that "still exists" on SUSE Linux. Thanks! This looks similar to the other bug I moved to you today timo. David, as of Beta5 syslog puts messages of NetworkManager to /var/log/NetworkManager. Please provide the output of this while connecting.
Additionally, please try connecting using GNOME applet ('np-applet') which comes with NetworkManager-gnome. This way we can figure whether this is a NM, nm-applet or KNetworkManager bug.
I used nm-applet with the same results. This is what I did and is shown in the log file I'll attach next: First I turned on my laptop, click on KNetworkManager icon I chose "Connect to Other Wireless Network" because the list showed just empty slots, Typed ESSID and encryption, on Advanced settings I chose protocol "AES". It got connected, I surf the web for 30 seconds and stoped working. The icon showed I was still connected but I couldn't ping anywhere. I quit "knetworkmanager" and started "nm-applet", this time it showed my wireless router on the list of Wireless Networks nevertheless I chose "Connect to Other Wireless Network" again BUT this time I chose Protocol "Automatic". nm-applet took 2 minutes and didn't connect at all, after that time it showed the "not connected" icon. I clicked again on nm-applet and chose my router from the list, asked me for the encryption key and this time I chose Protocol "AES". It got connected I surfed the web for 30 secs and stoped working again. The applet showed it was still connected. All these steps are showed in the attachment. Created attachment 70569 [details] /var/log/NetworkManager log file of the operations described on Comment #7 Thanks for the details, David. Joe, did you encounter similar problems with NM and ndiswrapper? Yes, besides a lot of other problems. My WPA-PSK connection also died, although much quicker. This is probably not a NetworkManager bug. If you're interested in stable connection, ndiswrapper might not be the right choice. David, could you try using ifup instead of NetworkManager and report if it is working more reliable? If this is not the case, I'm happy to hand over the bug to the maintainer of ndiswrapper :-) Weired enough I was using ifup with ndiswrapper without any problems until 2 days ago that I upgraded some packages (kernel and others) and now ifup is not working anymore. I'll try to downgrade the kernel and test ifup again OK, thanks! Please be aware of switching the interface to be controlled by ifup again (e.g. using YaST). Other than that, ifup will try to trigger NetworkManager for it. No it is not working with ifup anymore, I tried many things but ifup and NM are dead on my laptop when using WPA Personal encryption What exactly happens when using ifup? when I do /etc/init.d/network restart when trying to connect to wlan0 it shows: "no IP address yet... backgrounding" and it never gives me an IP address Could you call 'wpa_cli status verbose' after setting the device up and attach the output? it shows: Selected interface 'wlan0.pid' Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused Ok, this nearly worked. ;-) Please try 'wpa_cli -iwlan0 status verbose'. What wireless card do you have ('hwinfo --netcard' shows the details)?
As soon as I changed from NM to ifup 'wpa_cli -iwlan0 status verbose' showed : wpa_state=DISCONNECTED I runned /etc/init.d/network restart and again wpa_cli and it showed: wpa_state=ASSOCIATING like ten minutes later keeps showing the same message. I'll attach what 'hwinfo --netcard' shows Created attachment 70907 [details]
this is what shows 'hwinfo --netcard'
Package 0.5.1cvs20060303 (just submitted) has several ndiswrapper workarounds that may help you out. But, indeed, ndiswrapper is in a sad state. You can grab the packages here, as well: http://primates.ximian.com/~rml/misc/NetworkManager/ I'll test it and I'll let you know. Thanks! (In reply to comment #23) > Package 0.5.1cvs20060303 (just submitted) has several ndiswrapper workarounds > that may help you out. But, indeed, ndiswrapper is in a sad state. > > You can grab the packages here, as well: > > http://primates.ximian.com/~rml/misc/NetworkManager/ > The new NM and nm-applet work WONDERFULLY. It gets connected and I've been surfing the net for almost 1 hour without any problems BUT KNetworkManager doesn't work at all. When I click on it shows "No network device found" and it doesn't show any wired nor wireless networks. If that gets fixed... I'll be as happy as I can be! :) Thanks for your work! Hey those are good news! Beside of having KNetworkManager not being working ;-) I assume you've used KNM after using nm-applet or even started both at the same time, right? This does not always work, please give it a try with a clean session to see whether KNM still doesn't show devices and networks. I got the same results, I quit nm-applet, end session, start a new session or restart computer and knetworkmanager starts and I get the same message. I tried starting knetworkmanager from a console and I got this message: org.freedesktop.NetworkManagerInfo already owned error updating device Ah, sure. Sorry, we've recently had an API change in NetworkManager which KNetworkManager is not yet aware of. Just let me finish my pizza and I'll get back to you with a fresh KNetworkManager version which will work. You are the man! Take your time... enjoy your pizza... and thanks again! Haha, "let me finish my pizza" f17-thoenig-140 NetworkManager-kde: IN PROGRESS - i386: building (on barbella, ETA at 18:23) Hmm, I think there is also time for a dessert. We really should work on the algorithm for the estimated time of arrival. Packages are ready: http://www.fh-augsburg.de/~thoenig/KNetworkManager/ David, please let me know whether everything is fine. Everything working fine captain! You guys are great. Thanks for everyting. Glad to hear, thanks for testing! New package submitted to autobuild. Fixed. |