[PATCH] wpa_supplicant: Honor initial bgscan timer
Jouni Malinen
j
Fri Aug 27 10:37:13 PDT 2010
On Thu, Aug 19, 2010 at 08:46:34AM -0700, Paul Stewart wrote:
> Honor the interval setup in bgscan_simple_init even if we
> get notified of a signal change. This prevents the system
> from doing a bgscan too early after connecting to a network
> (for example, during DHCP)
After some more thought and experiments with this, I agree that we
should not trigger a new scan based on the initial signal change event
that is indicated immediately after the threshold value is configured.
However, that event should still update the bgscan interval and I don't
think that we should skip the signal change events for the full short
interval after initialization.
I used a bit different approach on achieving the skipping of the new
scan (which I believe was the main operation you wanted to avoid here)
while still using the signal change events:
http://w1.fi/gitweb/gitweb.cgi?p=hostap.git;a=commitdiff;h=1e6ef6455cd4c4213c269fa843ab53d9b392baf4
Please let me know if this does not resolve the issue for you.
--
Jouni Malinen PGP id EFC895FA
More information about the Hostap
mailing list