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

Dan Williams dcbw at redhat.com
Wed Dec 2 15:52:45 EST 2009


On Tue, 2009-12-01 at 10:45 +0100, Holger Schurig 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. 
> 
> No it's not. In my environment, a moving client can get VERY 
> different APs with very different signal strengths after 10 
> Seconds.

I'd asked you about this back on October and you never said anything :)
So the problem then is that the re-scan is pointless depending on the
situation; but we don't have supplicant API to express when the
controller thinks its pointless and when the controller thinks its
relevant.  Thoughts?

Note that this wouldn't affect *roaming* at all, simply initial network
association.  I think the tradeoff ends up being a slightly longer
initial association for the forklift case against a shorter connect time
for any slower-moving or stationary client.

Dan




More information about the HostAP mailing list