-
Notifications
You must be signed in to change notification settings - Fork 71
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] Cannot use wpa3-personal for 802.11s mesh #254
Comments
@SerialVelocity we need to add |
I think another issue is the 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. |
@SerialVelocity can you look whether this patch correctly adds support for WPA3 in mesh mode?
Doesn't mfp have to be optional in mixed mode? Can it be required and work on WPA2 too? Not sure I understood 100%. |
I think it adds it correctly. I'm running the docker images of openwisp so I'm not sure how to try deploying your patch. Afaik, the "pmf is required" extension came before wpa3 was a thing: 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) |
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. |
Done! |
Closes #254 Co-authored-by: Federico Capoano <f.capoano@openwisp.io>
It seems wpa3-personal (not sure if mixed is possible as well) is missing from the schema:
https://github.com/openwisp/netjsonconfig/blob/1.0.2/netjsonconfig/schema.py#L400-L404
Is there a way of setting this manually and bypassing the checks? Usually, you can override fields by specifying "unknown properties" but the "encryption" key is re-used here.
The text was updated successfully, but these errors were encountered: