[Gutsy] Unable to connect to Access Point if encryption method (WEP/WAP/WAP2) of the AP is changed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Baltix) |
Invalid
|
Undecided
|
Unassigned | ||
network-manager (Ubuntu) |
Invalid
|
Low
|
Unassigned | ||
network-manager-applet (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: network-manager
Gutsy 64-bit Tribe-5 + updates to 17th September 2007.
network-manager Version: 0.6.5-0ubuntu11
I've been happily running two Linksys Wifi access points (WRT54GL & WAP54G) with WPA-PSK using the stock Linksys firmware. Because the WAP54G couldn't support WPA2 I had them both set to use WPA-Personal.
Today I decided to replace the firmware in both with the latest dd-wrt:
WAP54G Firmware: DD-WRT v24 RC-3 (09/13/07) micro - build 7957
WRT54GL Firmware: DD-WRT v24 RC-3 (09/13/07) vpn - build 7957
I then enabled WPA2-Personal on both.
NetworkManager just couldn't get a connection and there weren't any clues. After a lot of trial-and-error I discovered it is possible to connect if both APs are set to WPA. I did some searching and found an email by Brain Millet in June to the Gnome Network Manager mailing list:
http://
In it Brian reports discovering that NetworkManager (or is it nm-applet?) tries to use the existing WPA network configuration stored by gconfd, rather than detecting the AP(s) are now wanting WPA2 and updating the connection method and key details. In effect it tries to use stale configuration values.
The solution is to delete the configuration. To report all known networks (ESSIDs) and then choose a single one do this:
$ gconftool -R /system/
To delete all networks:
$ gconftool --recursive-unset /system/
or to delete just <essid>
$ gconftool --recursive-unset /system/
or, using gconf-editor navigate to:
/system/
Select the network name and in the right-pane delete each of the keys.
Now use nm-applet to reconnect to the network. A dialog will appear asking for the "WPA2-Personal" pass-phrase. Type it in and NetworkManager will connect and save the new settings.
From now on WPA2 connections will work.
Changed in network-manager (Baltix): | |
status: | New → Invalid |
I believe a similar thing happened to me when I changed from using WEP to WPA on my access point.