Comment 6 for bug 594676

Revision history for this message
goink (dchomyn) wrote :

I have the same "bad passwwrd" reply using WPA with a preshared key on 1.7.0, as part of Ubuntu 10.10

I believe this may be a problem interaction between wicd and the way wpa_supllicant is passing the (preshared) key to the network authority (your router).

In my case, I have a Linksys WRT54GL running DD-WRT v24-sp2 (10/10/09) std - build 13064 OpenSource firmware, configured as an Access Point in Mixed mode (b/g)

I have no problem authinticating WPA Personal TKIP or AES from Windows or Mac OS X clients with a variety of wireless adapters (Linksys, D-Link, Lucent, Airport (Mac)).

Wth wicd 1.7.0 and wpasupplicant 0.6.10-2 (wext as wpa_supplicant driver selected in wicd by default) on Linux 2.6.35.-24-generic (Ubuntu) and a Lucent Orinoco Gold 802.11b wireless adapter I am able to connect initialy (one time) without the "bad password" error.

After the initial successful connection, reconnection is not possible (again, the "bad password" error) ***unless the wireless security settings on the router are re-applied. Once reapplied, a subsequent attempt to create a wireless connection from the Linux client will succeed without any changes having been mad on the client side.

The psk data being sent to the router (with respect to the Wireless security settings) is being cached in such a way the connection is initially possible but defeats subsequent attempts at connection when the same psk data is sent again? Or, perhaps, the passkey is cached/stored on the client side (after it is used to make the first connection) in such a way that it will be sent incorrectly upon subequent attempts at connection? Of course, I'm simply guessing, here ... it is by luck that I found the workaround to establish this connection.

BTW, FYI, I am unable to use the Gnome Network-Manager to establish any wireless connections at all.