GNOME Bugzilla – Bug 646210
impossible to connect to WPA2 wifi networks, from either Network panel or gnome-shell
Last modified: 2011-04-19 06:18:18 UTC
When trying to connect to WPA2 networks (either WPA2-AES or WPA2-PEAP), I get "Device activation failed: (32) Failed to determine AP security" on stdout and can't configure it. this is with NM 0.8.997 + all f15 patches from git, on openSUSE live image
Can you grab 'iwlist wlan0 scan' output and 'nm-tool' output for the AP in question?
I've did more test and my initial report was incorrect : -on WPA2-AES (or even WPA), I can activate the network only one time (either using g-s extension or g-c-c network panel). I get NM popup to enter passphrase. If I cancel it, I can no longer get it back and get "Device activation failed: (32) Failed to determine AP security" - on WPA-Enterprise, I go directly to "Device activation failed: (32) Failed to determine AP security"
Can I still get some iwlist scan output for the home WPA AP? Also, for the home AP when you say "If I cancel it, I can no longer get it back and get..." do you mean that if you cancel the dialog, and you try to click the AP again from the menu, then it gives the "failed to determine AP security" error?
I'll give you the output tonight. Yes, if I click it on g-s extension, I get the "failed to determine AP security message". And in g-c-c network panel, I can't even change the network itself (combobox is acting as it is disabled.
New test (based on gnome-shell 2.91.93 + NM 0.8.997 + g-c-c 2.91.93): - I can always activate home WPA AP from g-s extension : if I cancel WPA passphrase dialog, I can choose the same AP from g-s and it works fine - when I try to do the same selection from g-c-c, I have failure. Here is the test scenario : * no wifi connection established * start "gnome-control-center network" * choose wireless * choose WPA home AP (combobox can be opened) * if this is the first time an AP was ever selected (either here or using g-s extension), you get WPA passphrase popup * otherwise (if you cancelled the passphrase popup previously), nothing appears on the UI but on stdout you get "Device activation failed: (32) Device not found", you don't get the WPA passphrase popup and "options" button isn't enabled * you can still do the activation of the AP from g-s extension scan for my home AP: Cell 01 - Address: 7e:53:f1:85:79:4c channel:3 Frequency: 2.422 Ghz (Channel 3) Quality=25/70 Signal level=-85dBm Encryption key:on ESSID:"blablabla" Bit Rates: 1Mb/s; 2Mb/s; 5.5 Mb/s; 11Mb/s : 9Mb/s ; 18Mb/s ; 36Mb/s ; 54Mb/s Bit Rates: 6Mb/s; 12Mb/s; 24Mb/s ; 48Mb/s Mode:Master Extra:tsf=000000dda8a2914c Extra: Last beacon: 484ms ago IE: Unknown: 000a57686974654c6f646765 IE: Unknown: 010882848b961224486c IE: Unknown: 030103 IE: Unknown: 2a0104 IE: Unknown: 32040c183060 IE: Unknown: 2D1a6e1017ffff0000001000... IE: Unknown 3d16030506000... IE: Unknown: 3e0100 IE: WPA version 1 Group cipher: CCMP Pairwise Ciphers (1): CCMP Authentication Suites (1): PSK
I have the same/a very similar problem. My universitie's WLAN uses WPA2 enterprise and I don't get any dialogue asking for credentials at all. Also trying to add the network by hand the "Save" button is greyed out. I'm around that network quite regularly should you need any information to debug this.
*** Bug 647115 has been marked as a duplicate of this bug. ***
New 802.1x/Enterprise connections (ie, connect to new AP from the menu) should be fixed as of 3166aaedfee96c5de88ba58b6bce4136c1249c5e.
reopening, I've applied patches 8f1689b1f4863c47f8a75e4297a2001e52c6e381 to 3166aaedfee96c5de88ba58b6bce4136c1249c5e to NetworkManager-gnome and only "old" nm-applet is fixed. Both gnome-shell extension and gnome-control-center network panel are still broken.
(In reply to comment #9) > reopening, I've applied patches 8f1689b1f4863c47f8a75e4297a2001e52c6e381 to > 3166aaedfee96c5de88ba58b6bce4136c1249c5e to NetworkManager-gnome and only "old" > nm-applet is fixed. Both gnome-shell extension and gnome-control-center network > panel are still broken. Well yeah, this bug was moved back to NetworkManager from gnome-shell, and now we either need to use this bug for gnome-shell too, or file a new one for gnome-shell and track the fix for the shell there... in reality the fix needed to be two places, both in nm-applet (to expose the bits necessary for the indicator to poke since the indicator doesn't yet provide a full NM client) and the indicator to twiddle nm-applet.
ok, I've cloned this bug for gnome-shell. Should I do the same for gnome-control-center too ?
I yeah, probably. The applet now has addition D-Bus API to facilitate the indicator and the control panel showing the applet's 802.1x UI. 22de0e2762a3e81a1bb73e4a48767741e5f26396
I've also cloned this bug for gnome-control-center network panel.