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

From: <bugzilla-noreply_at_freebsd.org>
Date: Sun, 03 Jul 2022 16:53:07 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238

J.R. Oldroyd <fbsd@opal.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #235053|0                           |1
        is obsolete|                            |

--- Comment #204 from J.R. Oldroyd <fbsd@opal.com> ---
Created attachment 235055
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=235055&action=edit
patch to have wpa_driver_bsd_associate() check for WLAN_EID_RSN IE before
setting WPA

Here's a 5th version.

This is the same functionality as the 4th version.  I just moved the duplicated
code into a new function wpa_driver_bsd_set_rsn_wpa_ie() which I then call from
each of the RSN and WPA sections.

I have tested with my one AP with a primary VAP of WPA2/RSN+WPA and a secondary
VAP which is OPEN.  Here are the three connections to show it associates in
each way:

        regdomain ETSI country NL authmode WPA2/802.11i privacy ON

        regdomain ETSI country NL authmode WPA privacy ON deftxkey UNDEF

        regdomain ETSI country NL authmode OPEN privacy OFF txpower 17

And, yes, it gets an IP and passes traffic in all three cases.

Not tested: WEP.  This AP doesn't support WEP.

It'd be great to get feedback from Jackie to know that this works there, too.

Jackie, if you are able to test this, I am testing with the stable/13 code with
none of the other earlier patches.  You should be able to reset to your
release/13.1.1 point and try with just this patch.

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