Date: Sun, 03 Jul 2022 15:57:08 +0000 From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 264238] wpa_supplicant 2.10 fails to associate to open secondary VAP when primary VAP is WPA Message-ID: <bug-264238-21060-OjnD9JYdrt@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-264238-21060@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 J.R. Oldroyd <fbsd@opal.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #235051|0 |1 is obsolete| | --- Comment #200 from J.R. Oldroyd <fbsd@opal.com> --- Created attachment 235053 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=235053&action=edit patch to have wpa_driver_bsd_associate() check for WLAN_EID_RSN IE before setting WPA Version 4 of this patch now also checks for the vendor_ie that indicates WPA1 is available. I duplicated the code. If WPA2/RSN is available, I set that. Else if WPA1 is available, I set that. There may be a more optimal way of coding it, e.g., by making a new function that is called from both RSN and WPA sections. I found that my one AP here does have a mixed WPA1+WPA2 mode, so I set that for the primary VAP. I have tested with config in wpa_supplicant.conf for both RSN and separately for WPA and it associates both ways. -- You are receiving this mail because: You are on the CC list for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-264238-21060-OjnD9JYdrt>