Thu Jul 21 08:19:18 PDT 2011
> 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
> wpa_supplicant does not control this behavior, so you would need to take
> a look at the driver to figure out why it is reporting the connection to
> be lost.
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.
I think the disconnects are initiated by wpa_supplicant. However, I
don't see any message from wpa_supplicant explaining the reason for
I believe it would be better to ask in the hostap list
(hostap at lists.shmoo.com)
You may want to add extra wpa_printf() calls in the code calling
wpa_blacklist_add() and maybe see the backtrace in gdb so that you see
what is going on. Perhaps wpa_supplicant could provide better information.
I don't think the driver plays any significant role here.
What do you think?
More information about the Hostap