[PATCH v3] Fix scan retry after a failure

[Kalle Valo]

Kalle Valo <kalle.valo at canonical.com> writes:

> With broadcom's "wl" driver the first scan always fails. (Apparently it also
> doesn't send scan results ready signals, but let's forget it for now.) With
> connman's five minute scan interval it meant that it would take five minutes
> from boot until a wireless connection was established.
>
> The reason is that currently wpasupplicant doesn't handle scan retries
> and it goes directly to INACTIVE state:
>
> 14:23:09 wpa_supplicant[1046]: Scan timeout - try to get results
> 14:23:09 wpa_supplicant[1046]: Failed to get scan results
> 14:23:09 wpa_supplicant[1046]: Failed to get scan results - try scanning again
> 14:23:09 wpa_supplicant[1046]: State: SCANNING -> INACTIVE
>
> Instead of going to INACTIVE set wpa_s->scan_req to make it explicit
> that this is a requested scan and fix check in wpa_supplicant_req_new_scan().
>
> This is based on Michael Terry's patch for wpasupplicant 0.6.x reported here:
>
> http://w1.fi/bugz/show_bug.cgi?id=374

For reference, comments for v2 are here:

http://lists.shmoo.com/pipermail/hostap/2010-November/021947.html

-- 
Kalle Valo