problems with Wireless event: new AP (00:00:00:00:00:00)

Sebastian Weitzel togg at togg.de
Tue May 17 11:55:51 EDT 2005


> For me, this is not an association with a bogus AP BSSID, but a
> disassociation from the current AP. If the driver is generating this
> event in a case where it is not actually being disassociated/
> deauthenticated, the driver should be fixed..

Maybe http://article.gmane.org/gmane.linux.drivers.hostap/10487 
allready tried to patch this issue. I applied the patch and retested. 
It still dont solves the problem. As you can see the ifindex differs 
which should lead to reject this event, but does not.


ifi->ifi_index=6
drv->ifindex(8) != ifi->ifi_index(6), reject event
fromlen=12 addr=00:00:00:00:00:00
ifi->ifi_index=8
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
Added BSSID 00:0b:6b:33:61:2e into blacklist
State: 4WAY_HANDSHAKE -> DISCONNECTED

I dont know yet why the wireless event still leads to blacklisting. 
Maybe the patch is incomplete.



-- 
Regards,
Sebastian Weitzel




More information about the HostAP mailing list