[Madwifi-devel] Re: problems with Wireless event: new AP (00:00:00:00:00:00)
Mon Jul 11 13:04:11 PDT 2005
sorry for responding so late.
i have now checked in a change to the madwifi driver (now working in HEAD
again, btw) which should fix this behaviour. i did as you suggested and send
a probe request to verify if the AP is still there.
On Sunday 29 May 2005 07:24, Jouni Malinen wrote:
> Because the driver is reporting a disassociation!
> I took a closer look at madwifi and what is happening (at least in my
> test case) is that the association is completed successfully, but
> Atheros mac reports a beacon miss and the driver interprets this as the
> AP has disappeared, which is not really the case here. This was
> relatively easy to reproduce at least with long beacon interval (1000
> This is starting to look like the most commonly reported problem with
> madwifi driver* when using wpa_supplicant and I would really appreciate
> it if someone would take a closer look at what is happening with beacon
> miss events. Either the hardware is configured incorrectly or there are
> bogus bmiss events. Either way, the driver should filter these out and
> not report disassociation. If the time sync for beacon miss cannot be
> fixed, the driver could, e.g., use probe request to verify whether the
> AP is still in range before processing the beacon miss event.
> *) see, e.g., http://hostap.epitest.fi/bugz/show_bug.cgi?id=44
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20050711/c8f34a72/attachment.pgp
More information about the Hostap