[Bug 264238] wpa_supplicant fails to associate to open unprotected 802.11n

2022-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #124 from Jaskie --- (In reply to Cy Schubert from comment #123) Tested. WiFi didn't work. /usr/sbin/wpa_supplicant -dd -i wlan1 -c /etc/wpa_supplicant.conf.open -D bsd 2>&1 | tee output.file output (~3min) uploaded. -- You a

[Bug 264238] wpa_supplicant fails to associate to open unprotected 802.11n

2022-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #125 from Jaskie --- Created attachment 234857 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=234857&action=edit output from wap 2.10 patched (2 patches) -- You are receiving this mail because: You are on the CC lis

[Bug 264238] wpa_supplicant fails to associate to open unprotected 802.11n

2022-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 Glen Barber changed: What|Removed |Added CC|g...@freebsd.org,|r...@freebsd.org,

[Bug 264238] wpa_supplicant fails to associate to open unprotected 802.11n

2022-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #127 from Cy Schubert --- (In reply to Jaskie from comment #125) Thank you. A different error message to work on now. (Sadly, not being able to reproduce this problem here is a disadvantage.) Hypothesis: I suspect the problem

[Bug 264238] wpa_supplicant fails to associate to open unprotected 802.11n

2022-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #128 from Cy Schubert --- Can everyone here please confirm security/wpa_supplicant also does not work. The port has disabled P2P support by default while base has it enabled. -- You are receiving this mail because: You are on

[Bug 264238] wpa_supplicant fails to associate to open unprotected 802.11n

2022-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #129 from Adrian Chadd --- heh, we shouldn't have p2p enabled until we have support for it. :-) -- 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

2022-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #130 from Cy Schubert --- Yeah, it's not the issue anyway. Read my next post. -- 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

2022-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #131 from Cy Schubert --- Hi Jackie, Reviewing one of your previous outputs (wpa_out_p1) we see: wlan0: Automatic auth_alg selection: 0x1 No supported operating classes IE to add wlan0: Trying to associate with 70:d9:31:0e:2c:

[Bug 264238] wpa_supplicant fails to associate to open unprotected 802.11n

2022-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #132 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=3e8eb5c7f4909209c042403ddee340b2ee7003a5 commit 3e8eb5c7f4909209c042403ddee340b2ee7003a5 Author:

[Bug 264238] wpa_supplicant fails to associate to open unprotected 802.11n

2022-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #133 from Adrian Chadd --- hm, so if the WPA IEs are /actually/ making it into the TXed frames and it's not a net80211 / driver bug somehow ew. Yes, it's common to have open + WPA VAPs. Heck, I do it at home sometimes for

[Bug 264238] wpa_supplicant fails to associate to open unprotected 802.11n

2022-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #134 from Cy Schubert --- Yes, but should it add those frames to the open VAP too? Can you check your equipment for the same "feature?" -- 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

2022-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #135 from Adrian Chadd --- a) it doesn't on a tplink b) it should not, no -- 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

2022-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #136 from Adrian Chadd --- oh crazy q - are the VAP MAC addresses different? Between the WPA and open VAPs? -- 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

2022-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #137 from Cy Schubert --- WRT one of my Netgear APs, no, they do not share the same MAC. However the 2.4 GHz and 5 GHz secondary VAPs share the same channel as their primary VAPs. Makes sense as the device has two radios. The o

[Bug 264238] wpa_supplicant fails to associate to open unprotected 802.11n

2022-06-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264238 --- Comment #138 from Jaskie --- (In reply to Cy Schubert from comment #131) I don't understand the tech stuff and code behind this. But I can confirm that there is only one WiFi hosted. We have different WiFi setup at different workplace