Bugzilla – Bug 156389
NetworkManager: Problems connecting to AP
Last modified: 2007-06-05 09:57:58 UTC
Hello, I experienced the following problems with when trying to use (K?)NetworkManager to use wireless internet. First, I use the packages from Beta6 and I am able to connect to my AP with NetworkManager. Sometimes, my access point simply do not appear on the list of knetworkmanager, sometimes there are wireless networks shown without a single ESSID. Here, usually restarting NetworkManager helps. Looking through the other NetworkManager Bugreports, I found recommondations to update NetworkManager (to 0.6.0cvs20060306). The result was no wireless networks were shown in KNetworkManager, even though nm-tool listed all available networks. (I updated KNetworkmanager as well, but it was the same version as in beta6) Another point I want to make is that when the initial attempt to connect to my access point fails, I get the Knetworkmanager dialog to connect to other wireless network, but the wrong one. My knetworkmanagerrc is as follows: ESSID=Egal Encryption=WEP HardwareAddresses=00:.... Timestamp=2006,3,8,23,51,42 Trusted=true WEPMethod=OpenSystem WEPType=ASCII Furthermore I am a bit confused that it is possible at this point to make my encryption key visible. I know that the key is stored in kwallet but here I need to have the password. I think a possible wrong encryption key must only be corrected in kwallet. I hope I did not reopen known bugs. Regards Stefan Arndt WEPType=ASCII
Please attach: /var/log/NetworkManager `hwinfo --wlan' `ifconfig'
*** Bug 156409 has been marked as a duplicate of this bug. ***
Created attachment 71978 [details] Output of hwinfo --wlan
Created attachment 71979 [details] Output of ifconfig
Created attachment 71980 [details] NetworkManager Log File
(In reply to comment #0) > NetworkManager (to 0.6.0cvs20060306). The result was no wireless > networks were shown in KNetworkManager, even though nm-tool > listed all available networks. (I updated KNetworkmanager as well, > but it was the same version as in beta6) Can you please try with nm-applet (NetworkManager-gnome) and report whether it shows the same behaviour? > Another point I want to make is that when the initial > attempt to connect to my access point fails, I get > the Knetworkmanager dialog to connect to other wireless network, > but the wrong one. Please define "wrong one". Wrong encryption scheme? I have fixed a couple of bugs with regard to this. RPMs are available at: http://nouse.net/projects/KNetworkManager/NetworkManager-kde-0.1r5842-1.i586.rpm http://nouse.net/projects/KNetworkManager/NetworkManager-kde-0.1r5842-1.src.rpm http://nouse.net/projects/KNetworkManager/NetworkManager-kde-debuginfo-0.1r5842-1.i586.rpm Prior using the new version of KNetworkManager I advise you to delete knetworkmanagerrc. You can also delete the already stored secrets for networks using kwalletmanager.
I have attached a couple of information regarding your questions. Unfortunately, installing http://nouse.net/projects/KNetworkManager/NetworkManager-kde-0.1r5842-1.i586.rpm leaves the system unusuable because KNetworkManager cannot find a single wireless AP. nm-tool (output attached) gives the correct information. The NetworkManager log file is attached as well. Furthermore attached are two screenshots of KNetworkManager connect dialog. Do I need to start gnome for nm-applet? gnome is not installed on my system, starting nm-applet from within a shell under kde does not work.
Created attachment 72625 [details] nm-tool output
Created attachment 72626 [details] NetworkManager logfile, starting with proposed version.
Created attachment 72627 [details] KNetworkManager dialog, showing wrong options
Created attachment 72628 [details] KNetworkManager dialog, showing correct options
Ah, sorry, you also need to update NetworkManager in order to use this version of KNetworkManager. Packages are available at: http://primates.ximian.com/~rml/misc/NetworkManager/ Could you please let me know if this helps? Thanks!
It looks like it works. But I experience a weird problem. nm-tool as well as KNetworkManager do not give me my AP, ESSID Egal. Wireless Networks (* = Current Network) orion: Infrastructure Mode, Freq 0.000 MHz, Rate 0 Mb/s, Strength 33%, Encrypted (WEP) WLAN: Infrastructure Mode, Freq 0.000 MHz, Rate 0 Mb/s, Strength 33% LindeVX8: Infrastructure Mode, Freq 0.000 MHz, Rate 0 Mb/s, Strength 50%, Encrypted (WEP) ALICE-WLAN: Infrastructure Mode, Freq 0.000 MHz, Rate 0 Mb/s, Strength 33%, Encrypted (WEP) Ohana: Infrastructure Mode, Freq 0.000 MHz, Rate 0 Mb/s, Strength 29%, Encrypted (WPA) Using connect to other network it connects to Egal, but Egal is shown with zeo strength and as hidden, which it is not. Wireless Networks (* = Current Network) orion: Infrastructure Mode, Freq 0.000 MHz, Rate 0 Mb/s, Strength 33%, Encrypted (WEP) WLAN: Infrastructure Mode, Freq 0.000 MHz, Rate 0 Mb/s, Strength 33% LindeVX8: Infrastructure Mode, Freq 0.000 MHz, Rate 0 Mb/s, Strength 50%, Encrypted (WEP) ALICE-WLAN: Infrastructure Mode, Freq 0.000 MHz, Rate 0 Mb/s, Strength 33%, Encrypted (WEP) Ohana: Infrastructure Mode, Freq 0.000 MHz, Rate 0 Mb/s, Strength 29%, Encrypted (WPA) *Egal: Infrastructure Mode, Freq 0.000 MHz, Rate 0 Mb/s, Strength 0%, Encrypted (WEP), Hidden I am currently working with KNetworkManager indicating zero strength.
(In reply to comment #13) > It looks like it works. Good. > But I experience a weird problem. nm-tool as well as KNetworkManager do not > give me my AP, ESSID Egal. > Using connect to other network it connects to Egal, but Egal is shown with zeo > strength and as hidden, which it is not. This is strange. I've never seen that before. Does the network show up after rebooting the system?
I looked a bit further into it. First, I managed to crash KNetworkManager. A trace is attached. I did it by using connect to other networks and just fill in my AP's ESSID (Egal) and pressing connect. Furthermore I have attached a nm-tool output again because at first nm-tool showed again my AP uses hidden ESSID, running nm-tool 10s later, all was correct. (I noticed that KnetworkManagers systray icon changed from white to blue, indicating full strength)
Created attachment 72745 [details] trace of knetworkmanager crash
Created attachment 72746 [details] Output of nm-tool
(In reply to comment #16) > Created an attachment (id=72745) [edit] > trace of knetworkmanager crash Could not reproduce this. Can you reproduce it? Other than that I see things being working as expected? Signal strength is being reported correctly and also the network isn't marked as hidden anymore.
I could reproduce the crash. After reboot, KNetworkManager could not see my ESSID. Dialog connect to other wireless network, typing Egal (my ESSID) and return, for a couple of seconds I see a message box, then the KDE crah manager. Well, things work as expected, at least kind of. Restarting KNetworkManager after the crash gave me my ESSID. Selecting Egal from the list of networks did not work, although Egal is setup in knetworkmanagerrc and the encryption key is stored in kwallet. Next step was to use the dialog connect to other .... . After manually entering the encryption key, the message box got up to 57% . After a while I got the connect to other ... dialog again. Select the proper encrytion method the message box got up to 57% again, gave me the dialog connect to other ..., after pressing return the knetworkmanager disappeared from the systray, then reappeared as not connected. Now I could select Egal from the network list and all worked. To me it looks like that knetworkmanager has problems when it takes a while (e.g. after switching on the AP) to connect to the AP. Regarding your question if the network appears after rebooting (comment #14) I experienced no difference wether I reboot or not or wether the AP was switched on before rebooting or switched on while or after rebooting.
Stefan, do you still see the crash with Beta 8? Otherwise, I'd consider this one as fixed.
Running beta8 I have not experienced a crash. I still do have the problem of knetworkmanager sometimes not showing ESSIDs.
Thanks for the update. From now on I'm refusing to show networks for which KNetworkManager did not receive ESSIDs. I'll upload RPMs for SVN r5927 in a couple of minutes. Would be nice if you could give them a try.
Here they are: http://nouse.net/projects/KNetworkManager/ Please let me know if this version works for you. Thanks!
I have installed it. So far it looks good. I will keep you informed if I experience problems. Thanks a lot! Stefan
Excellent news! Closing as fixed.