Thu Jul 21 08:57:51 PDT 2011
On Thu, Jul 21, 2011 at 04:19:18PM +0100, Nejc ?koberne wrote:
> > That is a disconnection event from the driver:
> > 1310857012.148471: Wireless event: cmd=0x8b15 len=20
> > 1310857012.148635: Wireless event: new AP: 00:00:00:00:00:00
> > 1310857012.148974: Setting scan request: 0 sec 100000 usec
> > 1310857012.149966: Added BSSID 00:17:df:2c:c9:e2 into blacklist
> > 1310857012.150280: CTRL-EVENT-DISCONNECTED - Disconnect event - remove
> > keys
> I posted the question to the madwifi list, and they disagree:
> My understanding is that wpa_supplicant doesn't like something about the
> AP because it adds the AP's MAC to the blacklist before the disconnect.
That is not what the debug log shows here. The first line there is the
disconnection event from the driver and that is followed by
wpa_supplicant blacklisting the BSSID (because of the driver
> I think the disconnects are initiated by wpa_supplicant. However, I
> don't see any message from wpa_supplicant explaining the reason for
That is not correct. The disconnect was indicated by the driver and the
reason for blacklisting was that driver event.
> I don't think the driver plays any significant role here.
> What do you think?
The information you received from the madwifi list seems to be based on
misinterpretation of the debug log. The disconnection event is clearly
coming from the driver, not from wpa_supplicant.
Jouni Malinen PGP id EFC895FA
More information about the Hostap