[Bug 264238] wpa_supplicant 2.10 fails to associate to open secondary VAP when primary VAP is WPA

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238

--- Comment #181 from Cy Schubert <cy@FreeBSD.org> ---
(In reply to Jaskie from comment #180)

Don't worry, it's no longer needed. I will be pushing the workaround patch
sometime tomorrow and will MFC it to stable/13 and stable/12 three days later.
re@ will merge it into releng/13 sometime after that to allow binary updates.

There are a number of Linux distros that also have similar, but not the same,
bugs reported. Unfortunately their users have not provided as much significant
detail as you have, for which I am very grateful to you for.

Currently Red Hat has a bug open for failure to associate (WPA2) with Broadcom
driver. Another with a Dlink AP. While here at FreeBSD I can reproduce the
problem with rtwn_usb(4) with a secondary VAP on my Netgear however my iwn(4)
works with that VAP. (FreeBSD uses the BSD driver while Linux uses the nl80211
driver.)

The wpa_supplicant port will also contain the patch and will be MFHed to 2022Q3
immediately. The wpa_supplicant29 port will obviously not. Neither will the
wpa_supplicant-devel port get the patch in order to allow me and others to
continue to work on this bug. (I typically use the -devel port, with its
bleeding edge wpa_supplicant, anyway, eating my own dogfood.)

I am grateful for your assistance, providing significant outputs (which reading
other orgs PRs outputs are relatively sketchy). Your help and patience has been
appreciated.

-- 
You are receiving this mail because:
You are on the CC list for the bug.