Page MenuHomeFreeBSD

wpa_supplicant workaround association failure with open secondary VAP
AbandonedPublic

Authored by cy on Jun 25 2022, 2:43 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Feb 2, 8:50 PM
Unknown Object (File)
Jan 20 2025, 1:20 PM
Unknown Object (File)
Jan 19 2025, 10:27 PM
Unknown Object (File)
Dec 15 2024, 1:25 PM
Unknown Object (File)
Nov 16 2024, 7:37 AM
Unknown Object (File)
Oct 2 2024, 7:16 PM
Unknown Object (File)
Sep 20 2024, 9:41 PM
Unknown Object (File)
Sep 20 2024, 6:13 PM

Details

Reviewers
adrian
bz
Summary

There has been a regression in wpa_supplicant 2.10 with APs with two VAPs. When the first or primary VAP is configured with WPA and a secondary open unprotected VAP, typically a guest SSID on commodity APs or at hotels and universities with the primary VAP configured with WPA for staff and the secondary VAP configured open for students or visitors.

The regression only occurs in this instance: when the primary VAP is configured for WPA and the secondary VAP is configured open.

The solution is a temporary workaround until a permanent solution can be developed, either by myself or by the hostap upstream w1.fi.org.

The bug is in wpa_supplicant 2.10 and has been confirmed by me also in Fedora 36.

Again, this is only a temporary workaround so that this bug can restore functionality to 13.1-RELEASE end users. A permanent solution will be worked on, initially with our upstream. Emails have been posted on lists.infradead.org. There are no replies yet.

See PR/264238 for a complete discussion of the bug.

Test Plan

The solution has been tested locally and in PR/264238.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped