Re: Problem with IEEE80211_MONITORING_INTERVAL

[Johannes Berg <johannes@sipsolutions.net>]

[-- Attachment #1: Type: text/plain, Size: 2478 bytes --]

Marcel,

> Trying to authenticate with 00:1f:3f:19:d8:b7 (SSID='Holtmann' freq=2462 MHz)
> Trying to associate with 00:1f:3f:19:d8:b7 (SSID='Holtmann' freq=2462 MHz)
> Associated with 00:1f:3f:19:d8:b7
> WPA: Key negotiation completed with 00:1f:3f:19:d8:b7 [PTK=CCMP GTK=CCMP]
> CTRL-EVENT-CONNECTED - Connection to 00:1f:3f:19:d8:b7 completed (auth) [id=0 id_str=]

> Associated with 00:1f:3f:19:d8:b7
> CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

> Associated with 00:1f:3f:19:d8:b7
> CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

> Associated with 00:1f:3f:19:d8:b7
> CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

> Associated with 00:1f:3f:19:d8:b7
> WPA: 4-Way Handshake failed - pre-shared key may be incorrect

> Associated with 00:1f:3f:19:d8:b7
> CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

> As you see it keeps scanning, authenticating, associating and then it
> never completes.

> And this is the debug output from the kernel side (latest
> wireless-testing with all debug options enabled):

> wlan0: associated

> wlan0: beacon loss from AP 00:1f:3f:19:d8:b7 - sending probe request
> wlan0: beacon loss from AP 00:1f:3f:19:d8:b7 - sending probe request
> wlan0: no probe response from AP 00:1f:3f:19:d8:b7 - disassociating
> phy0: Removed STA 00:1f:3f:19:d8:b7
> phy0: Destroyed STA 00:1f:3f:19:d8:b7
> wlan0: authenticate with AP 00:1f:3f:19:d8:b7
> wlan0: authenticated
> wlan0: associate with AP 00:1f:3f:19:d8:b7
> wlan0: associate with AP 00:1f:3f:19:d8:b7
> wlan0: RX ReassocResp from 00:1f:3f:19:d8:b7 (capab=0x431 status=0 aid=2)
> wlan0: associated
> phy0: Allocated STA 00:1f:3f:19:d8:b7
> phy0: Inserted STA 00:1f:3f:19:d8:b7

So far so good

> wlan0: deauthenticated (Reason: 2)

This is confusing. And it keeps happening:

> wlan0: associated

> wlan0: deauthenticated (Reason: 2)

> wlan0: RX ReassocResp from 00:1f:3f:19:d8:b7 (capab=0x431 status=0 aid=2)
> wlan0: associated

> wlan0: deauthenticated (Reason: 2)

> wlan0: RX ReassocResp from 00:1f:3f:19:d8:b7 (capab=0x431 status=0 aid=2)
> wlan0: associated

> wlan0: deauthenticated (Reason: 2)

> Do you need anything else? I have really no idea what happens here and I
> like to get it fixed.

Can you do the kernel log with timing please? It seems strange to get
"previous authentication is no longer valid" from the AP as a reason
code while associated.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]