On 09/15/2010 07:24 AM, Johannes Berg wrote:
On Wed, 2010-09-15 at 07:21 -0700, Ben Greear wrote:
Right, but as soon as one finished, the next would start, and at least in .31,
that caused the first to un-associate, giving never-ending loop of interfaces
scanning and trying to associate.
There should be a grace period maybe?
I don't think that really fixes anything, except make the race between
full scan and attempting for the first interface to associate harder to
hit (and that is only useful if the scan-one logic is enabled anyway).
Ok, I'll see if I can add a 'scan-one-if-associated' flag for wpa-supplicant to
use.
Just make it give the channel instead of adding new API.
I think you still need an 'any', because whoever wrote the wpa_supplicant config file doesn't
necessarily know what channel the AP is on. The first interface to do a full scan
can figure that out and associate....
Thanks,
Ben
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
