Wed Apr 23 09:53:25 PDT 2008
On Wed, 2008-04-23 at 18:44 +0200, Lars Ericsson wrote:
> Currently this is what happens most of the time, when all ioclts had been
> issued from the driver, it drops current authentication/association atempts
> and start with the new one. Most of the times that works fine.
> But sometimes, when for any reason the 3 ioctls get delayed, the driver may
> success to associate with the old BSSID (since that is still valid in the
> driver). Then when all 3 ioctls has been received, including the new BSSID,
> the driver re-starts the authentication/association sequence with the new
> The problem is that the STA already have a valid association with the first
> AP. In this case the new BSSID silently ignores any
> authentication/association attempts. My believe is that it knows that the
> STA already have a valid association.
Uh huh. Aren't we disassociating when we change to a new bssid?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 828 bytes
Desc: This is a digitally signed message part
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20080423/ab5af58a/attachment.pgp
More information about the Hostap