[PATCH] Avoid unnecessary triggering of rescans

Helmut Schaa hschaa
Wed Feb 27 08:53:52 PST 2008

Am Mittwoch, 27. Februar 2008 17:26:15 schrieb Dan Williams:
> > If you are connected to an AP and start a scan using iwlist it's a bit
> > annoying to see wpa_supplicant either triggering a lot of scans (0.5.8)
> > or starting a reassociation (0.5.10).
> That's odd; why should the supplicant even bother reassociating, or
> triggering scans if scan results just come in without a request?

That was the intention for my patch :)

> Doesn't it just say something like "Already associated with selected AP"
> and do nothing?  That's what I usually see.

In my opinion it should, yes.

The setup here is a bit complex, I have multiple hidden APs with the same 
ESSID around.

Once wpa_supplicant gets the scan-results (not being the scan initiator) it 
tries to find a suitable AP. If it finds the one you're currently associated 
with it drops the message "Already associated..." and does not do anything 

Otherwise it starts a new scan. Once it starts a scan for a specific ESSID it 
will get the currently associated AP but in my case there are even more APs 
which match the ESSID and wpa_supplicant will start associating with the 
first matching AP.

Perhaps it would be even better to do nothing when scan-results come in and 
wpa_supplicant is not in state WPA_SCANNING.


More information about the Hostap mailing list