wpa_supplicant not dettecting association?

[Daniel Benoy]

Also, I rebooted the thing and it got an IP just fine.  (!?)  Also I see that it got alerted through the wpa_cli action stuff at boot time just like I was expecting it to do earlier...

I'm working on the theory that the timeout in wpa_supplicant is too short.. it would explain the flakyness.  Unfortunately the timeout value is hard coded, so I'll have to mess around to test that.

also 'iwconfig eth0 power off' seems to make the issues go away.  All this intermittant behavior is reinforcing my theory that the timeout is too short and various factors make the time it takes shorter or longer causing intermittant behavior.

Shame on wpa_supplicant for not making the timeout configurable.

On Thursday 05 March 2009 13:25:03 you wrote:
> Hi.  I'm not sure if this represents a bug or not so I wanted to get your opinions.
> 
> I'm trying to get network connections to come up automatically with Debian's wpa_cli action script, but wpa_cli is not detecting connections and doesn't call the script.
> 
> I'm at work and I'm connecting to a nearby open access point, and here's what I see when I run wpa_cli manually.
> 
> ----
> lisa:~# wpa_cli -i eth0
> wpa_cli v0.6.4
> Copyright (c) 2004-2008, Jouni Malinen <j at w1.fi> and contributors
> 
> This program is free software. You can distribute it and/or modify it
> under the terms of the GNU General Public License version 2.
> 
> Alternatively, this software may be distributed under the terms of the
> BSD license. See README and COPYING for more details.
> 
> 
> 
> Interactive mode
> 
> > <2>CTRL-EVENT-SCAN-RESULTS 
> <2>Trying to associate with 00:11:95:54:96:8b (SSID='kitsune' freq=2427 MHz)
> <2>Authentication with 00:11:95:54:96:8b timed out.
> 'PING' command timed out.
> Connection to wpa_supplicant lost - trying to reconnect
> Connection to wpa_supplicant re-established
> <2>CTRL-EVENT-SCAN-RESULTS 
> <2>Trying to associate with 00:11:95:54:96:8b (SSID='kitsune' freq=2427 MHz)
> <2>Authentication with 00:11:95:54:96:8b timed out.
> 'PING' command timed out.
> Connection to wpa_supplicant lost - trying to reconnect
> Connection to wpa_supplicant re-established
> <2>CTRL-EVENT-SCAN-RESULTS 
> <2>Trying to associate with 00:11:95:54:96:8b (SSID='kitsune' freq=2427 MHz)
> <2>Authentication with 00:11:95:54:96:8b timed out.
> .
> .
> .
> ----
> 
> However, shortly after wpa_supplicant started trying to authenticate, I saw this in dmesg:
> ----
> AR6000 connected event on freq 2427 with bssid 00:11:95:54:96:8b  listenInterval=100, beaconInterval = 100, beaconIeLen = 0 assocReqLen=29 assocRespLen =30
> Network: Infrastructure
> ----
> 
> ??
> 
> I actually am connected too.  I can run dhclient manually and get an IP.  So it seems like the association occurs, but it doesn't send the proper signal to wpa_supplicant.  I expected to see something like this: (grabbed from a mailing list)
> ----
> <2>Trying to associate with 00:0e:38:0d:07:76 (SSID='ssid' freq=2447 MHz)
> <2>Associated with 00:0e:38:0d:07:76
> <2>CTRL-EVENT-EAP-STARTED EAP authentication started
> <2>CTRL-EVENT-EAP-METHOD EAP method 13 (TLS) selected
> <2>CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
> <2>WPA: Key negotiation completed with 00:0e:38:0d:07:76 [PTK=TKIP GTK=TKIP]
> <2>CTRL-EVENT-CONNECTED - Connection to 00:0e:38:0d:07:76 completed (auth)
> ----
> (Only since it's an unsecured access point, it should skip directly to CTRL-EVENT-CONNECTED after it associates, I imagine)
> 
> The relevent lines in my wpa_supplicant.conf are:
> ----
> network={
>        key_mgmt=NONE
>        priority=-9999999
> }
> ----
> 
> I'm using the Om2008.12 kernel and modules (to boot Debian)
> 



-- 
Daniel Benoy
http://daniel.benoy.name