Ubuntu
network-manager package

  1. Bug #263963
  2. Comment #76

Comment 76 for bug 263963

Revision history for this message
Sewi (sebastian-willing) wrote : Re: [iwl*] intel drivers take overly long to associate to WPA for some hardware

System: Samsung NC10
Chip: Atheros AR242x
Modul: ath5k

Test 1: Associate with WEP-PSK - AP 1
ESSID could not be found during scanning. Others (including WinXP on the same computer) show the WLAN and associate without problems. Setting up the connection manually didn't solve it.

Test 2: Associate with WEP-PSK - AP 2
ESSID is found during scanning. The key entered via gui (26 chars HEX => 13 bytes) is changed during the connection try. "sudo iwconfig wlan0 essid foo key bar..." accepts the key but doesn't associate anyway. I think that I saw a short association in "iwconfig wlan0" but it disappeard immed. The AP has a MAC filter and showed the clients MAC in his "stations" list for a short moment before I added the client to the allowed-MAC-list.

[ 6802.294692] wlan0: direct probe to AP 00:0e:2e:2e:37:1d try 1
[ 6802.296511] wlan0 direct probe responded
[ 6802.296539] wlan0: authenticate with AP 00:0e:2e:2e:37:1d
[ 6802.298898] wlan0: authenticated
[ 6802.298924] wlan0: associate with AP 00:0e:2e:2e:37:1d
[ 6802.300994] wlan0: RX AssocResp from 00:0e:2e:2e:37:1d (capab=0x421
status=0 aid=1)
[ 6802.301043] wlan0: associated
[ 6802.301572] wlan0: disassociating by local choice (reason=3)
[ 6805.314274] wlan0: deauthenticated

There is no "WPA" option, just "WEP" and "WPA2". I guess, speaking WPA2 to a WPA device won't work.