[Bug 264238] wpa_supplicant fails to associate to open unprotected 802.11n
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #115 from rkober...@gmail.com --- (In reply to Cy Schubert from comment #105) I'm about to rebuild with the latest wps_supplicant. Just to clarify, does this refer to connecting to an AP supporting 11n or the supplicant attempting to associate at 11n (which I assume includes 11ng.) I ask because iwlwifi(4) has no 11n capability at this time. Also, jaskie seems to have already provided the information I collected yesterday, but I do want to confirm that the issues does apply to iwlwifi(4) and rtwm(4). Both work with 2.9, but neither work with the base supplicant. I will note that the iwlwifi seemed to crash a lot when I tried using it with the base system supplicant. rtwn had no such issues. Thanks for your everyone, especially cy, for all of their work on this very annoying bug! -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 264238] wpa_supplicant fails to associate to open unprotected 802.11n
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #116 from Cy Schubert --- The difference between an open AP that my rtwn(4) can associate to and one it cannot is: associates; wpa_driver_bsd_associate: ssid 'KQNGN3' wpa ie len 0 pairwise 1 group 1 key mgmt 4 Does not associate: wpa_driver_bsd_associate: ssid 'Golden_Pond' wpa ie len 13 pairwise 1 group 1 key mgmt 4 The Information Element appears to cause it to use WPA on an open network. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 264238] wpa_supplicant fails to associate to open unprotected 802.11n
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #117 from Cy Schubert --- (In reply to rkoberman from comment #115) I'd be interested in seeing this line of output from wpa_supplicant -dd wpa_driver_bsd_associate: ssid 'Golden_Pond' wpa ie len 13 pairwise 1 group 1 key mgmt 4 Seems that an IE supplied by the AP causes wpa_supplicant to attempt to associate using WPA against an open AP, even when the config file says key_mgmt=NONE. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 264238] wpa_supplicant fails to associate to open unprotected 802.11n
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #118 from Cy Schubert --- Under wpa_supplicant 2.9 the AP in question prints, wpa_driver_bsd_associate: ssid 'Golden_Pond' wpa ie len 0 pairwise 1 group 1 key mgmt 4 Notice that there is no IE. 2.9 ignores the IE whereas 2.10 does not. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 264238] wpa_supplicant fails to associate to open unprotected 802.11n
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #119 from Cy Schubert --- So the plot thickens. Golden_Pond, is an open guest network I created on my DMZ AP. Removing the guest SSID and opening up the DMZ AP entirely resolves the problem. So, what does this mean? An open network will not have an IE. However an AP which has a primary WPA SSID and a secondary (like a guest SSID) which is open will broadcast a WPA IE. And, wpa_suppliant uses that to communicate its WPA IE. wpa_supplicant takes that to mean it's WPA protected. So the question is, what in wpa_supplicant changed tfor an open network with key_mgmt=NONE for it to override key_mgmt? I will post this to the hostap mailing list. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 264238] wpa_supplicant fails to associate to open unprotected 802.11n
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #120 from Adrian Chadd --- Cy, does it do that on freebsd as an AP? that's ... kinda wrong? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 264238] wpa_supplicant fails to associate to open unprotected 802.11n
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #121 from Cy Schubert --- (In reply to Adrian Chadd from comment #120) I haven't tried FreeBSD as an AP yet. The "bug" is on a Netgear router (used as a router in my DMZ). It normally has one SSID (my wife's SSID). Adding a guest network to it causes the problem. Looking at WHU-STU, this is not the case. wlan0: 9: 70:d9:31:0e:2c:00 ssid='WHU-STU' wpa_ie_len=0 rsn_ie_len=0 caps=0x21 l evel=-70 freq=2432 In other words I have not been able to reproduce this problem here because my testing has exposed a bug in this Netgear router. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 264238] wpa_supplicant fails to associate to open unprotected 802.11n
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #122 from Cy Schubert --- (In reply to Adrian Chadd from comment #120) Using it with an open FreeBSD hostapd AP works perfectly. wpa_ie is zero. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 264238] wpa_supplicant fails to associate to open unprotected 802.11n
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #123 from Cy Schubert --- Created attachment 234848 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=234848&action=edit Remove upstream cc79eb725f7b564269619ce4a64be2a80927d392 Can everyone please try this patch. If you're running 13.1-RELEASE you will also need to include the patch at https://bugs.freebsd.org/bugzilla/attachment.cgi?id=234807&action=edit. -- You are receiving this mail because: You are on the CC list for the bug.
