[PATCH] wpa_supplicant: Implement fast-associate on SelectNetwork
pstew at chromium.org
Wed Jan 16 12:28:29 EST 2013
The big difference in wpa_supplicant_fast_associate() right now is that it
turns into a no-op if the selected network
(from wpa_supplicant_pick_network()) doesn't match the ssid chosen in
wpa_supplicant_select_network(). It didn't seem right to me for some other
network to be connected if select_network was unambiguous. It's likely a
non-concern for me, so I'll drop it in a v3.
On Wed, Jan 16, 2013 at 8:56 AM, Jouni Malinen <j at w1.fi> wrote:
> On Wed, Jan 16, 2013 at 06:59:14AM -0800, Paul Stewart wrote:
> > I considered wpas_select_network_from_last_scan(), but I wondered whether
> > the calls to wpa_supplicant_rsn_preauth_scan_results on old scan results
> > everything in the "else" clause for "if (selected)" was valid in this
> > If you're okay with a hard-coded time limit like
> interworking_reconnect, I
> > can do that. Also let me know if you're unconcerned by any side effects
> > the rest of wpas_select_network_from_last_scan().
> If there are undesired side effects from
> wpas_select_network_from_last_scan(), those need to be fixed for
> Interworking case anyway, so yes, I'd like to see a single mechanism to
> be used and any possible issues with it getting resolved. These two
> cases are pretty much identical in the sense that both of them may have
> run through a scan recently and could re-use information from it. The
> Interworking one is guaranteed to have run through a scan, but these can
> be handled with the same implementation with the use of that time limit.
> The actual time limit value could end up becoming a configurable
> parameter in the future, but a hard-coded limit would be fine as an
> initial step.
> Jouni Malinen PGP id EFC895FA
> HostAP mailing list
> HostAP at lists.shmoo.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the HostAP