I'm a beginner and followed the instructions here: https://openwrt.org/docs/guide-user/network/wifi/mesh/rapiddeployment
But the instructions are too barebones. The install works on my Google Wifi Mesh nodes, and I can get into the interface, but I don't see any mesh interface or network? What do I do after booting up? Do I need to manually set up a mesh after that and SSIDs for clients?
Do I do the same set up on each node?
Yes, same secret on all mesh nodes.
It is very clear and concise. Just fill in the two custom text boxes in the Firmware Selector, generate and download. Flash. Boot them up with just one of them with its wan port connected by ethernet to a lan port on your isp router.
You should see ssids looking like OpenWrt2gxxxx etc.
Try connecting.
If you stick with the example ipv4 address you should get an ip address in the 192.168.9.xx range.
SSH to 192.168.9.1 and you will be on the portal node.
Run mesh11sd status to see what you get.
The mesh config CANNOT be seen from luci as it is a dynamic config, whereas luci is concerned only with static configs.
ok this is really helpful, thank you! running mesh11sd status shows that it's up. but then how do i create a ssid clients can connect to? both of my wireless ssid's say "wireless is not associated"
Where do you see this?
The ssids should be up automatically.
On the portal node (the one with the ethernet upstream connection - wan to isp lan), show the output of
mesh11sd status
and
iwinfo
Thanks for taking the time to help. I have 2 nodes set up with the same image (setup exactly with the instructions on the website). They don't seem to connect to each other and there's no SSID.
Nothing happens when I type iwinfo.
When I type mesh11sd status I get the following:
{
"setup":{
"version":"4.1.1",
"enabled":"1",
"procd_status":"not running",
"portal_detect":"1",
"portal_detect_threshold":"0",
"portal_channel":"default",
"channel_tracking_checkinterval":"30",
"mesh_basename":"m-11s-",
"auto_config":"1",
"auto_mesh_network":"lan",
"auto_mesh_band":"2g40",
"auto_mesh_id":"ad96569faef7a1295f33a0790c8782",
"mesh_gate_enable":"1",
"mesh_leechmode_enable":"0",
"mesh_gate_encryption":"0",
"txpower":"",
"mesh_path_cost":"10",
"mesh_path_stabilisation":"1",
"checkinterval":"10",
"interface_timeout":"10",
"ssid_suffix_enable":"1",
"debuglevel":"1"
},
"interfaces":{
}
}
And this is what wireless looks like in Luci
Luci will not show the mesh11sd config. Mesh11sd creates a dynamic config but luci only understands static configs.
Hint: When you are posting the outputs of commands etc., these are pre-formatted, so you have to enclose the text between two pairs of three backtics, or copy then higlight the text and click the </> symbol on the top line of the text box you are writing in.
If you can, please show the output of:
service mesh11sd restart; logread -e mesh11sd -f
I get the following
root@OpenWrt:~# service mesh11sd restart; logread -e mesh11sd -f
Sun Feb 9 00:07:58 2025 daemon.notice mesh11sd[23226]: mesh11sd is in startup
Sun Feb 9 00:08:14 2025 daemon.notice mesh11sd[23226]: mesh11sd v4.1.1 has started: mesh management mode 1
Sun Feb 9 00:08:14 2025 daemon.err mesh11sd[23226]: Unable to autoconfigure. Please install ath10k NON ct drivers for mesh support
Sun Feb 9 00:08:24 2025 daemon.notice mesh11sd[24979]: mesh11sd is in startup
Sun Feb 9 00:08:40 2025 daemon.notice mesh11sd[24979]: mesh11sd v4.1.1 has started: mesh management mode 1
Sun Feb 9 00:08:40 2025 daemon.err mesh11sd[24979]: Unable to autoconfigure. Please install ath10k NON ct drivers for mesh support
Sun Feb 9 00:08:50 2025 daemon.notice mesh11sd[26622]: mesh11sd is in startup
Sun Feb 9 00:09:06 2025 daemon.notice mesh11sd[26622]: mesh11sd v4.1.1 has started: mesh management mode 1
Sun Feb 9 00:09:06 2025 daemon.err mesh11sd[26622]: Unable to autoconfigure. Please install ath10k NON ct drivers for mesh support
Sun Feb 9 00:09:16 2025 daemon.notice mesh11sd[28357]: mesh11sd is in startup
Sun Feb 9 00:09:32 2025 daemon.notice mesh11sd[28357]: mesh11sd v4.1.1 has started: mesh management mode 1
Sun Feb 9 00:09:32 2025 daemon.err mesh11sd[28357]: Unable to autoconfigure. Please install ath10k NON ct drivers for mesh support
Sun Feb 9 00:09:42 2025 daemon.notice mesh11sd[29999]: mesh11sd is in startup
Sun Feb 9 00:09:57 2025 daemon.notice mesh11sd[29999]: mesh11sd v4.1.1 has started: mesh management mode 1
Sun Feb 9 00:09:58 2025 daemon.err mesh11sd[29999]: Unable to autoconfigure. Please install ath10k NON ct drivers for mesh support
Sun Feb 9 00:10:08 2025 daemon.notice mesh11sd[31726]: mesh11sd is in startup
Sun Feb 9 00:10:23 2025 daemon.notice mesh11sd[31726]: mesh11sd v4.1.1 has started: mesh management mode 1
Sun Feb 9 00:10:23 2025 daemon.err mesh11sd[31726]: Unable to autoconfigure. Please install ath10k NON ct drivers for mesh support
Sun Feb 9 00:10:34 2025 daemon.notice mesh11sd[909]: mesh11sd is in startup
Sun Feb 9 00:10:49 2025 daemon.notice mesh11sd[909]: mesh11sd v4.1.1 has started: mesh management mode 1
Sun Feb 9 00:10:49 2025 daemon.err mesh11sd[909]: Unable to autoconfigure. Please install ath10k NON ct drivers for mesh support
Sun Feb 9 00:11:00 2025 daemon.notice mesh11sd[2558]: mesh11sd is in startup
Sun Feb 9 00:11:15 2025 daemon.notice mesh11sd[2558]: mesh11sd v4.1.1 has started: mesh management mode 1
Sun Feb 9 00:11:15 2025 daemon.err mesh11sd[2558]: Unable to autoconfigure. Please install ath10k NON ct drivers for mesh support
Sun Feb 9 00:11:26 2025 daemon.notice mesh11sd[4284]: mesh11sd is in startup
Sun Feb 9 00:11:41 2025 daemon.notice mesh11sd[4284]: mesh11sd v4.1.1 has started: mesh management mode 1
Sun Feb 9 00:11:41 2025 daemon.err mesh11sd[4284]: Unable to autoconfigure. Please install ath10k NON ct drivers for mesh support
Sun Feb 9 00:11:52 2025 daemon.notice mesh11sd[6010]: mesh11sd is in startup
Sun Feb 9 00:12:07 2025 daemon.notice mesh11sd[6010]: mesh11sd v4.1.1 has started: mesh management mode 1
Sun Feb 9 00:12:07 2025 daemon.err mesh11sd[6010]: Unable to autoconfigure. Please install ath10k NON ct drivers for mesh support
Sun Feb 9 00:12:18 2025 daemon.notice mesh11sd[7739]: mesh11sd is in startup
Sun Feb 9 00:12:33 2025 daemon.notice mesh11sd[7739]: mesh11sd v4.1.1 has started: mesh management mode 1
Sun Feb 9 00:12:33 2025 daemon.err mesh11sd[7739]: Unable to autoconfigure. Please install ath10k NON ct drivers for mesh support
Sun Feb 9 00:12:33 2025 daemon.info procd: Instance mesh11sd::instance1 s in a crash loop 11 crashes, 16 seconds since last crash
This is self explanatory.
Are these devices Google WiFi (Gale)?
If so, in Firmware selector, top text box, "Installed packages",
you need:
ath10k-board-qca4019 -ath10k-firmware-qca4019-ct ath10k-firmware-qca4019 base-files ca-bundle dnsmasq dropbear firewall4 fstools -kmod-ath10k-ct kmod-ath10k kmod-gpio-button-hotplug kmod-leds-gpio kmod-nft-offload kmod-usb-dwc3 kmod-usb-dwc3-qcom kmod-usb3 libc libgcc libustream-mbedtls logd mtd netifd nftables odhcp6c odhcpd-ipv6only opkg ppp ppp-mod-pppoe procd-ujail uboot-envtools uci uclient-fetch urandom-seed urngd -wpad-basic-mbedtls partx-utils mkf2fs e2fsprogs kmod-fs-ext4 kmod-fs-f2fs kmod-google-firmware kmod-ramoops luci wpad-mesh-mbedtls kmod-nft-bridge mesh11sd
Note the -ct packages have a minus sign in front of them and the non-ct packages are added. Also, similarly -wpad-basic-mbedtls with wpad-mesh-mbedtls replacing it.
Finally kmod-nft-bridge and mesh11sd are added.
Add the same stuff you did before to the Script to run on first boot (uci-defaults) box.
Hi @Bort1313 ,
never mind! I have gone through the exact same learning curve (including the ct driver issue) 
Once you have understood the instructions and have it properly setup and configured, it's working like a charm!