Bug 216136 - KNetworkManager does not correctly handle WPA/WPA2 PSK or EAP security for wireless networks
Summary: KNetworkManager does not correctly handle WPA/WPA2 PSK or EAP security for wi...
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: Network Management
Classification: Miscellaneous
Component: Wireless (show other bugs)
Version: 0.9
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Will Stephenson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-25 19:15 UTC by Kris Wong
Modified: 2011-05-08 20:10 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Kris Wong 2009-11-25 19:15:33 UTC 
Version:            (using KDE 4.3.3)
Compiler:          gcc 4.4.2 
OS:                Linux
Installed from:    Archlinux Packages

I have tried a number of different connection methods with a number of different networks. Below is a brief synopsis.

At the office, we have 2 wireless network and a wired network. I am able to connect to the wired network using networkmanager with no issues. I am also able to connect to the wireless networks by configuring them manually with ifconfig/iwconfig/wpa_supplicant. 1 wireless network is a guest network and uses WPA-PSK, the other uses WPA2-EAP with PEAP authentication. I cannot connect to either wireless network with networkmanager when using knetworkmanager.

I have 1 wireless network at home. It uses WPA2-PSK. I can also connect to this network when configured manually, but not with networkmanager/knetworkmanager.

Some googling around revealed others having issues with knetworkmanager. I uninstalled knetworkmanager from my system and installed the gnome networkmanager applet instead. After rebooting my computer, I was able to setup network manager to connect to either wireless network at my office with no problems.
Comment 1 A.C.Heron 2009-11-26 15:13:42 UTC 
*** This bug has been confirmed by popular vote. ***
Comment 2 Scott 2009-12-18 19:21:14 UTC 
I too have this problem,
Additional information would be that our network is WPA2-EAP PEAP MSCHAPv2 and hidden SSID. The network manager will not scan hidden SSID'd without prior scanning manually with;

iwlist wlan0 scan essid XXXXX

After which, networkmanager will see the SSID but still fails to attach with the same symptoms as previously described.

K Desktop Environment
Version 4.3.4 (KDE 4.3.4) "release 2"
Suse 11.2 64 bit

I will try the gnome fix as stated before but please don't make me use gnome.... I hate gnome almost as much as I hate windows ( oh Lord save me I had to say the "W" word ) aaaahhhh.
Comment 3 Scott 2009-12-18 19:40:27 UTC 
Confirmed, gnome network manager connects properly to hidden ssid wpa2-eap wireless network.
Comment 4 Will Stephenson 2010-01-05 17:43:55 UTC 
Kris, are your networks also hidden?
Comment 5 Kris Wong 2010-01-05 17:49:54 UTC 
My home network does not broadcast. Both networks at my office broadcast.
Comment 6 K Woelfel 2010-05-25 21:28:15 UTC 
I think maybe Bug 235541 is a duplicate of this bug.
Comment 7 K Woelfel 2010-05-25 21:31:04 UTC 
sorry, please ignore my las post
Comment 8 Lamarque V. Souza 2011-04-08 19:50:27 UTC 
Is this still happening?