CHROMIUM: wpa_supplicant: Abort associations on ASSOC_REJECT events Change wpa_supplicant to respond to AP triggered association failures by locally aborting the association process. For instance, certain enterprise AP's return status code 17 (too many STAs) and reject association requests when a particular AP has too many associated devices. Locally aborting the association process lets wpa_supplicant begin roaming immediately rather than waiting for the authentication timeout to fire. This is similar to the behavior triggered when the driver does in fact support separate authentication and association requests. BUG=chrome-os-partner:14543 TEST=Walk around a building with multiple APs serving the same ESS and some APs refusing associations with code 17. Note that roaming to an overbooked AP now immediately triggers an attempt to roam to a better AP, rather than waiting the 5 seconds for the authentication attempt to timeout. Change-Id: Ib715796fe770943c1206808d6ba503438c4d7bf6 Reviewed-on: https://gerrit.chromium.org/gerrit/35033 Tested-by: Christopher Wiley <wiley@chromium.org> Reviewed-by: Paul Stewart <pstew@chromium.org> Reviewed-by: mukesh agrawal <quiche@chromium.org> Commit-Ready: Christopher Wiley <wiley@chromium.org> Reviewed-on: https://gerrit.chromium.org/gerrit/35230 Reviewed-by: Christopher Wiley <wiley@chromium.org>
1 file changed
