WPA3 Mesh11sd not showing

Installing and Using OpenWrt Network and Wireless Configuration
1

Hello - I am using a Ubituiti RocketM2 and the newest firmware I could get to work on this specific one is openwrt-19.07.9-ath79-generic-ubnt_rocket-m-squashfs-factory (due to flash chip model). When I install wpad-mesh-wolfssl, wpad-mesh-openssl, or wpad-wolfssl I cannot get WPA3-SAE to show up. This is the only encryption that I have been able to use with Mesh11sd. all of the other encryption options show an error and do not allow to proceed.

this is an XM model and I have it working on other XM models with 22.03.2 firmware (again, can't run 22.03.2 since the flash chip won't save settings) and XW models with the 19.07.9 firmware.

Any ideas how I can get WPA3-SAE as an option on this firmware?

2

To be clear:

  • Version 19 did not have mesh11sd - the Wiiki page seems to note you can install the IPKs from another version that does
  • You may wish to ask @bluewavenet - he is the maintainer of the package
3

Thank you. I did install Mesh11sd manually from the downloaded package from another version. which worked on the other XW 19.07.9 firmware. maybe I need to grab a different Mesh11sd package.

4

Show up where? Luci?

As mesh11sd is pure ash script it MIGHT work on 19.7, but I do not recall it being tested. I cannot think of any particular reasons it will not work, but who knows......
It is unfortunate you are stuck on 19.7.

WPA3-SAE is not a valid option for mesh. You will have to try the uci command to set encryption to sae in lower case.

5

On checking the internal development git repository, there was some testing on 19.7.
It originates from a proprietary version dating back to 18.06.

The consensus here is your best chance is to download v3.0.0beta:

It "should" do all the config for you. Worth a try anyway.

6

Thanks for taking a look @bluewavenet!

yes. In Luci.

WPA3-SAE isn't valid for mesh? that seems to be the only option I am able to select within Luci GUI. I have not tried running anything in command prompt.

7

The encryption standard developed for 802.11s mesh is known as sae-aes, shortened to "sae" in configuration files.
This predates the development of wpa3 by a number of years.
WPA3 was developed from the mesh sae-aes specifically for access point to client encryption and the end result is similar.

What matters is the correct encryption "type" is entered into the config.
For mesh, the type is "sae". Does the underlying driver sort out incorrect type? In some cases maybe.... I have not looked into the detail.