Closed ayrstone closed 3 months ago
Same result using wpad-mesh-wolfssl and wpad-mesh-openssl.
wireless.mesh.encryption='psk2'
Should be sae or none , use luci if in doubt.
I had wondered about that, so I used wireless.mesh.encryption='psk2', 'psk', and 'sae' - they all yielded the same result:
root@OpenWrt:/tmp/run# cat wpa_supplicant-phy0-mesh0.conf
network={
ssid="d7e8b340b41d54a7"
key_mgmt=SAE
mode=5
fixed_freq=1
frequency=2437
disable_ht40=1
disable_vht=1
noscan=1
sae_password="xxxxxxxxxx"
beacon_int=100
}
Since it seems to be so flexible, for laughs I tried encryption='woof' and it turns out that's a synonym for 'none'
Thanks anyway!
OK, I think this turned out to be a n00b problem. Searching around, I found this thread:
https://forum.openwrt.org/t/mesh-encryption-doesnt-work-on-mi-router-3-pro/106610
I had uninstalled wpad-basic, but not rebooted, so it remained in memory. Stupidly, I thought it would flush and reload.
After rebooting, it appears wpad-mesh-mbedtls does work... y'know, if you let it. :-)
Thanks again!
Trying to set up encrypted mesh in Snapshot downloaded today. 2.4 GHz. radio on with AP and mesh interfaces, 5 GHz. radio off. Wireless config:
Config does correctly generate /var/run/wpa_supplicant-phy0-mesh0.conf:
but generates errors in the logfile:
I tried the same config on an Alfa N2Q (ath79) and verified that it works in the same snapshot build, so it appears to be unique to this platform.