[PATCH] don't re-scan on SELECT_NETWORK with recent scan results

Sam Leffler sleffler
Mon Nov 30 09:19:55 PST 2009

On Sun, Nov 29, 2009 at 3:37 PM, Dan Williams <dcbw at redhat.com> wrote:

> It's pretty pointless to trigger a new scan when a control interface
> calls SELECT_NETWORK if the scan results are less than 10 seconds old.
> This speeds up associations when the connection manager has already
> requested a scan to determine what BSS to connect to, and then tells the
> supplicant to select that BSS, which previously would trigger yet
> another scan a few seconds after the first one.
It's difficult for me to tell from the patch but in my experience you want
to treat the scan results as a cache and age entries out and/or flush
explicitly under certain conditions.  This appears to be something short of

There's also the issue that this process may already take place below
wpa_supplicant in which case you don't want it doing the same work.

Related to this whole issue is that the d-bus api needs to provide better
control over scanning and likely also split out scanning from MLME
operations like associate.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20091130/68876c11/attachment.htm 

More information about the Hostap mailing list