Wifi mesh failure

happy holidays,
I have an ArcherC7 and EX6130 running openwrt 23.05.5 which I'm failing to mesh with 802.11s. I cannot get them to connect/show up in associated stations. The EX6130 doesn't show any problems in logread. I've tried with and without WPA3-SAE encryption. I've tried with wpad-mesh-mbedtls and wpad-mesh-worfssl. The Archer is throwing these errors

Sun Dec 22 12:51:37 2024 daemon.notice netifd: radio0 (4757): WARNING: Variable 'data' does not exist or is not an array/object
Sun Dec 22 12:51:38 2024 daemon.notice hostapd: Set new config for phy phy0:
Sun Dec 22 12:51:38 2024 daemon.notice wpa_supplicant[1487]: Set new config for phy phy0
Sun Dec 22 12:51:39 2024 daemon.notice wpa_supplicant[1487]: Set new config for phy phy0
Sun Dec 22 12:51:39 2024 daemon.notice hostapd: Set new config for phy phy0:
Sun Dec 22 12:51:39 2024 daemon.notice wpa_supplicant[1487]: Set new config for phy phy0
Sun Dec 22 12:51:41 2024 kern.warn kernel: [  724.116554] ath10k_pci 0000:00:00.0: 10.1 wmi init: vdevs: 16  peers: 127  tid: 256
Sun Dec 22 12:51:41 2024 kern.info kernel: [  724.133344] ath10k_pci 0000:00:00.0: wmi print 'P 128 V 8 T 410'
Sun Dec 22 12:51:41 2024 kern.info kernel: [  724.139620] ath10k_pci 0000:00:00.0: wmi print 'msdu-desc: 1424  sw-crypt: 0 ct-sta: 0'
Sun Dec 22 12:51:41 2024 kern.info kernel: [  724.148603] ath10k_pci 0000:00:00.0: wmi print 'alloc rem: 24984 iram: 38672'
Sun Dec 22 12:51:41 2024 kern.warn kernel: [  724.221643] ath10k_pci 0000:00:00.0: pdev param 0 not supported by firmware
Sun Dec 22 12:51:41 2024 kern.warn kernel: [  724.252815] ath10k_pci 0000:00:00.0: must load driver with rawmode=1 to add mesh interfaces
Sun Dec 22 12:51:41 2024 daemon.info dnsmasq[1]: read /etc/hosts - 12 names
Sun Dec 22 12:51:41 2024 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 4 names
Sun Dec 22 12:51:41 2024 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
Sun Dec 22 12:51:42 2024 kern.warn kernel: [  725.816174] ath10k_pci 0000:00:00.0: 10.1 wmi init: vdevs: 16  peers: 127  tid: 256
Sun Dec 22 12:51:42 2024 kern.info kernel: [  725.832950] ath10k_pci 0000:00:00.0: wmi print 'P 128 V 8 T 410'
Sun Dec 22 12:51:42 2024 kern.info kernel: [  725.839448] ath10k_pci 0000:00:00.0: wmi print 'msdu-desc: 1424  sw-crypt: 0 ct-sta: 0'
Sun Dec 22 12:51:42 2024 kern.info kernel: [  725.847770] ath10k_pci 0000:00:00.0: wmi print 'alloc rem: 24984 iram: 38672'
Sun Dec 22 12:51:42 2024 kern.warn kernel: [  725.912583] ath10k_pci 0000:00:00.0: pdev param 0 not supported by firmware
Sun Dec 22 12:51:42 2024 kern.warn kernel: [  725.927501] ath10k_pci 0000:00:00.0: must load driver with rawmode=1 to add mesh interfaces
Sun Dec 22 12:51:43 2024 daemon.err wpa_supplicant[1487]: Could not set interface phy0-mesh0 flags (UP): Invalid argument
Sun Dec 22 12:51:43 2024 daemon.err wpa_supplicant[1487]: nl80211: Could not set interface 'phy0-mesh0' UP
Sun Dec 22 12:51:43 2024 daemon.notice wpa_supplicant[1487]: nl80211: deinit ifname=phy0-mesh0 disabled_11b_rates=0
Sun Dec 22 12:51:43 2024 daemon.err wpa_supplicant[1487]: phy0-mesh0: Failed to initialize driver interface
Sun Dec 22 12:51:43 2024 daemon.notice wpa_supplicant[1487]: phy0-mesh0: CTRL-EVENT-DSCP-POLICY clear_all
Sun Dec 22 12:51:43 2024 daemon.notice netifd: Wireless device 'radio0' is now up
Sun Dec 22 12:51:44 2024 daemon.warn odhcpd[1711]: No default route present, overriding ra_lifetime!

On both routers: iw list | grep mesh * mesh point * #{ managed, AP, mesh point } <= 8, * mesh point * #{ IBSS } <= 1, #{ managed, AP, mesh point, P2P-client, P2P-GO } <= 8,
Can anybody help please?

I'm stoopid

Without looking in detail, my guess is that you are using the default ath10k-ct drivers. These drivers, depending on actual hardware/chipset will either work very poorly or not at all on a mesh interface.
Try replacing the ct drivers with the non-ct versions.

I'm stoopid

Did you replace both
kmod-ath10k-ct
and
ath10k-firmware-qca988x-ct
with the non-ct versions?

@bluewavenet OK, you are clearly correct. Thanks for insisting.
After installing the non-CT kmod AND the firmware packages, both 2.4Ghz and 5Ghz mesh seems to be working well.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.