Date: Sat, 02 Jul 2022 13:51:58 +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-eoujpC6zDo@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 --- Comment #175 from J.R. Oldroyd <fbsd@opal.com> --- (In reply to Bjoern A. Zeeb from comment #174) Hmm. I am looking at IEEE 802.11-2016 in section 9.4.2.1 (pg 784). Element ID 127 is defined as: Extended Capabilities (see 9.4.2.27) Element ID 255 is defined as: Reserved for elements using the Element ID Extension field Section 9.4.2.27 (pg 890) describes the Extended Capabilities element. EID 255 indicates the WLAN_EID_EXT_* values. EID 127 indicates the WLAN_EXT_CAPAB_* values. So, I may have been confused with wpa_supplicant's use of _EXT_ to mean both "EXTension field" and "EXTended Capabilities". I will need to research further to see if there is a third function for checking IEs with WLAN_EXT_CAPAB_* values. Or if there should be. That said, I can confirm that this patch is associating with both the OPEN secondary and the WPA primary (given appropriate config wpa_supplicant.conf). Perhaps that was just a coincidence. I need to go out shortly to run some errands for a few hours but will do some additional analysis and testing when I get back. -- 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-eoujpC6zDo>