Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] "management frame protection" can no longer be set to required for certain encryptions #264

Closed
SerialVelocity opened this issue Apr 30, 2023 · 1 comment · Fixed by #267

Comments

@SerialVelocity
Copy link

Split out from #254

SerialVelocity:
another issue is the 2 has been removed from:
https://github.com/openwisp/netjsonconfig/blob/1.0.2/netjsonconfig/schema.py#L496

which affects wpa2/wpa3 mixed mode. Quite a big issue if you have multiple SSIDs because if you have a WPA3 SSID with required 802.11w, and a WPA2/WPA3 mixed mode SSID with optional 802.11w, then your speed will drop from ~770Mbps to ~150Mbps.

nemesisdesign:
Doesn't mfp have to be optional in mixed mode? Can it be required and work on WPA2 too? Not sure I understood 100%.

SerialVelocity:
Afaik, the "pmf is required" extension came before wpa3 was a thing:
https://en.wikipedia.org/wiki/IEEE_802.11w-2009

I can't find anywhere that says pmf has to be optional for mixed mode as it can already be required for just wpa2. Could you point me to where you have seen that be the case? (I haven't explicitly tried connecting with wpa2 when mixed mode is enabled and pmfs are required)

nemesisdesign:
I can't find the information anymore right now, can you please create a separate issue for this other subject? We should look at what LuCI (the web interface of OpenWrt) does and just follow along.

Another thing that I noticed is that the "options" block still lists required as a valid title, but just the 2 option was removed.

@nemesifier
Copy link
Member

Thanks for reporting @SerialVelocity, #267 should fix it.
The bug was introduced by a seemingly unintentional mistake, at least this is my conclusion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants