[Pkg-utopia-maintainers] Bug#575014: Similar issue (but password-related)

[Alexandre Ratti]

Hello, 


I ran into a similar issue today with a Freebox v5 ("Freebox Crystal"
subscription).

I realize the issue is not fully identical as I could associate to
the wireless access point, whereas association failed in the first
message posted above.

I'm sending this report in case it's useful to solve similar problems.

I created a Wifi local network with WPA (TKIP + AES) security and set a
long password using the password-generation tool on the Free account
pages ("Ma Freebox" > "Paramétrer mon réseau Wifi").

This generated password contained a large number of special characters.

I was unable to connect to the Wifi network from a Debian GNU/Linux
(Squeeze) laptop with Network Manager. The four-way handshake always
failed, though I checked and rechecked the password.

Jan 29 18:28:07 portable NetworkManager[4761]: <info> (wlan0):
supplicant connection state:  associating -> associated
Jan 29 18:28:07 portable NetworkManager[4761]: <info> (wlan0):
supplicant connection state:  associated -> 4-way handshake
Jan 29 18:28:13 portable kernel: [27406.987013] wlan0: deauthenticated
from ee:de:4f:b8:6b:94 (Reason: 15)
Jan 29 18:28:13 portable wpa_supplicant[2085]: WPA: 4-Way Handshake
failed - pre-shared key may be incorrect
Jan 29 18:28:13 portable wpa_supplicant[2085]: CTRL-EVENT-DISCONNECTED
- Disconnect event - remove keys

"Reason 15" is "4-way handshake timeout".

I changed the password to a 50-chars string mixing lowercase chars,
uppercase chars and digits (no special chars). After rebooting the
Freebox, I was abe to connect from the Linux Squeeze laptop.

Users of other OSes met similar issues :

http://forum.hardware.fr/hfr/reseauxpersosoho/WiFi-et-CPL/probleme-freebox-wifi-sujet_20446_1.htm
http://www.commentcamarche.net/faq/11656-impossible-de-se-connecter-au-reseau-wifi-chiffre-en-wpa

In both cases removing special chars from the network key fixed the
problem.

So I don't think this is related to the Network Manager. It could be a
Freebox v5 issue.


Cheers.

Alex