Another thing I noticed is that in Windows and Linux (KDE Neon), identify the mesh network with WEP security and not with WPA2 as in a router with OpenWRT.
I also found that the generated wpa_supplicant-mesh0.conf uses the password from option key in the wireless file not from "option sae_password". If I omit "option key" in the wireless file, even though I set a password in "sae_password", sae_password" in wpa_supplicant is blank, so I don't think option sae_password in /etc/config/wireless is used.
Apart from encryption which I'm not sure if it is working right the mesh connection works fine and I also have an access point running on the same radio (phy0)
Got mine working with with these settings. I had to activate hwnocrypt=1 for my ath9k device (wzr-hp-g300nh), connected with a mt7621 device (xiaomi router 3g) on 2.4Ghz network.
Like mjs said, Web Ui tells me encryption is "none" when the mesh is conected otherwise WPA2.
My mesh link worked perfectly fine on a windows machine without that, but when I tried it on a linux box, for some reason I couldn't get a connection, so I added mesh0 to the lan ifname and that fixed it.
I thought the problem might be IPv4 / IPv6 related, or possibly dhcp, I guess there's probably something wrong elsewhere in my config.
Now that I got it working on very cheap ZBT WE1226 AP's, I'd like to try it on dual radio AP's, having the mesh on one frequency, and the AP's on the other.
I've tested it with about 10 devices connecting to the remote AP's, streamed videos and movies on a Fire Stick and a Chromecast, and everything works fine.
I've read somewhere about disabling the Spanning Tree protocol on the bridge, but I'm not sure how to do that on my configuration, or if it's even necessary.
Here is some Freifunk notes on the topic ``` mesh_fwding='0'
https://jenkins.kbu.freifunk.net/files/node-config/doc/
It is from a script. Node-Config
6.2. Using IEEE 802.11s
You can use the new IEEE 802.11s mesh mode instead of the new ad-hoc. To do so, you need to modify wireless.sh .
Modication to wireless.sh - example for radio0 (first radio, 2.4 Ghz usually).
# ...
set wireless.wifi_mesh='wifi-iface'
set wireless.wifi_mesh.device='radio0'
set wireless.wifi_mesh.network='mesh babel_mesh'
set wireless.wifi_mesh.mode='mesh'
set wireless.wifi_mesh.mesh_id='42:42:42:42:42:42'
set wireless.wifi_mesh_fwding='0'
set wireless.wifi_mesh.mcast_rate='12000'
# ...
When modifying the 5 Ghz network, use wifi_mesh5 instead of wifi_mesh .
Setting mesh_fwding='0' disables forwarding in the IEEE 802.11s mesh network. Forwarding is disabled , because Babel and batman-adv need to see the topology on their own. Forwarding would hide the structure of network from both babel and batman-adv. In addition, it is redundant to batman-adv.
If experimenting with IEEE 802.11s mesh forwarding:
Disable batman-adv - directly attach the mesh interfaces to the Freifunk bridge
Try to make babeld using the overlay metric
Avoid re-transmitting babel messages - IEEE 802.11s will distribute them anyway.