Bugzilla – Bug 144938
wireless encryption key
Last modified: 2006-03-16 22:21:50 UTC
When I put my wireless encryption key into NetworkManager it doesn't connect and when I bring the page back up the key is blank again. This also happens when I try to insert the key using iwconfig and disabling networkManager. For the network manager I put the key in and click on connect. It goes through the connection process in the second pop-up window and when that window disappears the first window with the key and the connect/cancel buttons is there. I then can only click on the cancel button. I'm using a netgear WG511 PCMCIA wireless card. With 10.0 I couldn't even bring up the card, the green light would constantly flash and iwconfig wouldn't ever show my access point. With 10.1 the green light is steady and with iwconfig I can see the access point, it just doesn't remember the encryption.
Last night I disabled NetworkManager and my encryption key was in the usual place when I went through yast's network card setup. When I brought the card back up everything worked so this is something inside NetworkManager.
NetworkManager does not use the YaST configuration for wireless, so the two are unrelated. Can you connect to wireless using ifup, without NetworkManager?
yes, I can connect my wireless card if I use the old setup using ifup and yast to configure the settings. Looking forward to using networkManager once it's finalized. looks very nice.
Can you provide NetworkManager's log during the attmept to connect to the wireless network? You can do this by stopping NetworkManager and doing NetworkManager --no-daemon > log or you can send your /var/log/messages.
Created attachment 65537 [details] output of NetowkrManager when trying to connect to a wireless network.
I've attached the output from the provided command. Once I killed my network manager, unplugged and re-plugged my wireless card in everything worked just fine without any kind of eth restarts.
Are you saying that everything works now? Also, what is this log from? This is not the output of "NetworkManager --no-daemon" ..
I ran the NetworkManager --no-daemon > log command and then tried to connect to my wireless network through network manager and it failed again. I then attached the information the log file to the bug. I have sence upgraded to beta2 and tried the network manager again, things looked more promissing, the window where I entered the encryption key disappeared once I entered the data and it asked me if I wanted to store the information in my KDE wallet. The progress bar went past configuring the devide to obtaining ip information but seemed to fail there (the window stayed at that progress position a long time and then just closed but never connected. When I kill Network manager and switch back to the old eth up/down system I can bring my netowrk card online that way. If I need to re-run the command and send you log output let me know, I'm not exactly sure what is supposed to be in there so I really don't have a way to verify if the data in the file is correct.
I am experiencing a similar problem. I have created a small film to show what happens: http://penguin.dq.fct.unl.pt/~jfraga/networkmanager.htm
I need the full log from NM. The above log is rather truncated. The full log is going to be long. Also, what driver? What is the details of the wireless network? Is it WEP? WPA? Broadcasting or non-broadcasting? Are both of you using KNetworkManager?
I'm using the prism54 driver, the network card is Netgear wg511. I do use WEP and it is broadcasting. The router is also a netgear router WGR614 v4. I can re-run the networkmanager app and collect the log again, I'm not sure how it would be longer, I started it up right before I tried the test and stopped it right after the test completed.
Can anyone experiencing this problem retest with NetworkManager version 0.5.1cvs20060207 (when it pops out), please? Make sure you restart the daemon or reboot, of course. It has a potential fix for random wireless problems.
Ping! Can anyone still reproduce this? Please retest with 0.5.1cvs20060214.
I was able to connect when wep is turned off. However when wep is on it still won't connect.
> Ping! Can anyone still reproduce this? > > Please retest with 0.5.1cvs20060214. I have finally retested with version 0.5.1cvs20060221 (from Beta 5) and the bug is still there. This time I decided to play with the access point settings: turned SSID broadcast on and off, turned WEP on and off, switched between Shared key and Open mode. Conclusion: I wasn't able to connect using Network Manager with any of those settings (even WEP turned off)... It could be something related with this particular access point because I have sucessfully connected to another AP using Beta 4's NM (with an issue https://bugzilla.novell.com/show_bug.cgi?id=141029 though) . BUT using the "Tradition Method with ifup" it works fine with this access point with or without WEP. So there is something wrong with NM.
Joao: What driver are you using? Gavin is prism54, right? Can you please test with 0.5.1cvs20060303? You can get them here, too: http://primates.ximian.com/~rml/misc/NetworkManager/ Let me know. Thank you!
yes, I was using prism54, but sorry, I had to go back to 10.0 for a stable version. Just too many problems to be using on my laptop I use every day. If there's a way to install the Network Manager under 10.0 I would try that, I liked the interface much better, now if it would only connect to encrypted networks.
(In reply to comment #16) > Joao: What driver are you using? I am using orinoco. My card is a Dell Truemobile 1150. I have tested with Beta6 and I have experienced the exact same behavior described in comment #9. Let me describe the tests I have done right after making a fresh install of Beta6: First, I configured the wireless access point for open access (no encryption). KNetworkManager connected fine. Second, I configured the AP for restricted security mode with a 128 bit WEP key. Now KNetworkManager wasn't able to connect. The behavior was exactly the same as shown in comment #9 film. What is annoying is that KNetworkManager doesn't seem to timeout. It sits there endlessly trying to connect. Third, I decided to revert the AP configuration to no encryption again. And now the second annoying thing happened: KNetworkManager wasn't able to connect (but it doesn't exit with an error message, instead it sits there endlessly trying to connect). It seems that KNetworkManager caches the WEP settings for a certain SSID and always uses them, even though the wireless network I am trying to connect to no longer needs WEP... How can a user clean KNetworkManager (or NetworkManager?) settings cache? I remind that connecting using WEP works without any problems using the traditional "if up" method.
Joao: Can you try the NM packages here: http://primates.ximian.com/~rml/misc/NetworkManager/ And see if they work with your orinoco card? Please reboot after installing the packages. Thanks. Let me know!
Alright, some of the issues are fixed, some of the issues are NEEDINFO'd. To consolidate the bugs and track the issues explicitly, please refer to bug #144268 for Orinoco issues and bug #154327 for Prism issues. I would appreciate if you could test with the latest SUSE beta and update the correct bug number as appropriate, either way. Thank you.