Thu Jul 21 11:21:37 PDT 2011
On Thu, Jul 21, 2011 at 01:02:48PM -0400, Pavel Roskin wrote:
> It contains such parts as:
> 1310857014.482037: RTM_NEWLINK: operstate=0 ifi_flags=0x1043 ([UP][RUNNING])
> 1310857014.482277: Wireless event: cmd=0x8b06 len=8
> 1310857014.482485: RTM_NEWLINK: operstate=0 ifi_flags=0x1043 ([UP][RUNNING])
> 1310857014.482715: Wireless event: cmd=0x8b04 len=12
> 1310857014.482924: RTM_NEWLINK: operstate=0 ifi_flags=0x1043 ([UP][RUNNING])
> 1310857014.483157: Wireless event: cmd=0x8b1a len=15
> 1310857024.464978: Authentication with 00:17:df:2c:c9:e2 timed out.
> 1310857024.468330: BSSID 00:17:df:2c:c9:e2 blacklist count incremented to 2
> 1310857024.468723: No keys have been configured - skip key clearing
> 1310857024.468881: State: ASSOCIATING -> DISCONNECTED
I would assume that the WEXT events here are triggered by the
wpa_supplicant association command that happened just before the lines
you listed here. However, the driver does not complete association
within ten seconds for some reason and the only way of figuring out what
the reason was would be to look at driver debug information (or
potentially a capture file from a sniffer).
> 1310857498.784927: Authentication with 00:17:df:2c:c9:e2 timed out.
> 1310857498.786611: BSSID 00:17:df:2c:c9:e2 blacklist count incremented to 2
> 1310857498.786967: No keys have been configured - skip key clearing
> 1310857498.787117: State: 4WAY_HANDSHAKE -> DISCONNECTED
This one would need a sniffer to see what exactly was transmitted.. It
looks like there could be mismatch in association state between the AP
and the station and reassociation not being reported to wpa_supplicant
or just some other odd frame loss that could end up with the station not
receiving all the frames. The AP seems to stop sending EAPOL-Key frames
(or well, at least they are not indicated all the way to
wpa_supplicant), but there is no disconnection event which should show
up if the maximum retry attempt is reached.
Jouni Malinen PGP id EFC895FA
More information about the Hostap