Ath10k-ct wifi-driver does not support 802.11s

Hi all,

I have two mesh nodes set up using 802.11s configuration using Archer C60 routers, following instructions in the link below.

https://cgomesu.com/blog/Mesh-networking-openwrt-batman/

Wireless drivers are kmod-ath10k-ct-smallbuffers which I see do not support mesh. Is there a alternative driver that can be installed, read some threads with similar problems but is a bit confusing? Is there a simple solution?

Cheers David

kmod-ath10k-smallbuffer and ath10k-firmware-qca9888 instead of the default -ct variants of these packages might help.

1 Like

Going to try that now,

Thanks

Why do you say it's not compatible? My understanding is that it is only for Wave-1 chips and Archer C60 is supposed to be Wave-2.

Just to make sure my understanding is correct;

Archer C60 does not support mesh 802.11s, is this true for both the Ath9 and Ath 10 drivers installed .

Therefore it is not possible to set up a 802.11s mes network no matter what software you install . Or is there a workable solution

Spent good few hours trying to install alternative to -ct but no joy.
Cheers

Thanks for your response

Only for 5Ghz chip (ath10k-ct) you have to change the driver. The 2.4Ghz (ath9k) is not necessary. I have also read that the CT version only supports 802.11s on Wave-2 chips and according to Qualcomm the Archer C60 has a Wave-2. If ath10k-ct-smallbuffers doesn't work, try ath10k-smallbuffers.

Cheers thanks for the advice, will try over the next few days

Ran into a number of problems with not enough space to download files,

Decided to build my own image, using following settings
Target system (Atheros ATH79)
Subtarget (Generic)
Target Profile (TP-Link Archer C60 v3)
Target image left as default.

Created the following image: openwrt-ath79-generic-tplink_archer-c60-v3-squashfs-factory.bin

Added the relevant packages for a mesh network. batman-adv, ath10k-smallbuffers, wapd-mesh

Tried to upgrade using luci and got an error. Was going to try flash image from the start reinstall the original firmware and work from there. Any advice appreciated?

David

Use the wpad-mesh-wolfssl package, not wpad.

Cheers thanks

Created an image using the steps below, I already destroyed one router forced upgrade using Luci,
now all I get is a green power light that stays on constantly. Have one new Archer C60 router with its own firmware installed? Is it safe to flash the image I created using the steps below? Leftmost settings as default only added batman-adv, wpad-mesh-wolfssl, ath10k-smallbuffers

Target system (Atheros ATH79)
Subtarget (Generic)
Target Profile (TP-Link Archer C60 v3)
Target image left as default.

# Download and update the sources
git clone https://git.openwrt.org/openwrt/openwrt.git
cd openwrt
git pull
 
# Select a specific code revision
git branch -a
git tag
git checkout v21.02.2
 
# Update the feeds
./scripts/feeds update -a
./scripts/feeds install -a
 
# Configure the firmware image and the kernel
make menuconfig
make -j $(nproc) kernel_menuconfig
 
# Build the firmware image
make -j $(nproc) defconfig download clean world

Is it safe to flash this image?

Will do my apologies

Can't see the 5g wireless driver after I built my own image.

<root@OpenWrt:~# opkg list-installed | grep -i ath/>

<ath10k-firmware-qca9888-ct - 2020-11-08-1/>
<kmod-ath - 5.4.188+5.10.110-1-1/>
<kmod-ath9k - 5.4.188+5.10.110-1-1/>
<kmod-ath9k-common - 5.4.188+5.10.110-1-1/>
<root@OpenWrt:~#/>````
When I run IP list I only get the 2g info. 

I'm I missing some dependencies? 
Any idea Franco what I'm missing.

With only one node set up is it possible to tell if it working or do I need two nodes. I already messed up one router and don't want to get a second until I'm sure it works or is this possible with only one set up?

Sun May  1 19:24:01 2022 daemon.notice netifd: Wireless device 'radio2' is now down
Sun May  1 19:24:05 2022 daemon.notice netifd: radio2 (4768): command failed: Link has been severed (-67)
Sun May  1 19:24:05 2022 daemon.notice netifd: radio2 (4768): command failed: Link has been severed (-67)
Sun May  1 19:24:06 2022 daemon.notice netifd: Wireless device 'radio2' is now up
Sun May  1 19:24:06 2022 daemon.notice netifd: Interface 'nwi_mesh0' is enabled
Sun May  1 19:24:10 2022 daemon.notice wpa_supplicant[1321]: mesh0: leaving mesh
Sun May  1 19:24:10 2022 kern.warn kernel: [ 5582.291330] ath10k_pci 0000:00:00.0: peer-unmap-event: unknown peer id 0
Sun May  1 19:24:12 2022 daemon.err wpa_supplicant[1321]: mesh0: mesh leave error=-134
Sun May  1 19:24:14 2022 daemon.notice wpa_supplicant[1321]: mesh0: interface state UNINITIALIZED->ENABLED
Sun May  1 19:24:14 2022 daemon.notice wpa_supplicant[1321]: mesh0: AP-ENABLED
Sun May  1 19:24:14 2022 daemon.notice wpa_supplicant[1321]: mesh0: joining mesh DavidQuinn
Sun May  1 19:24:15 2022 daemon.notice wpa_supplicant[1321]: mesh0: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=0 id_str=]
Sun May  1 19:24:15 2022 daemon.notice wpa_supplicant[1321]: mesh0: MESH-GROUP-STARTED ssid="DavidQuinn" id=0
Sun May  1 19:24:15 2022 daemon.notice netifd: Network device 'mesh0' link is up
Sun May  1 19:24:15 2022 daemon.notice netifd: Interface 'nwi_mesh0' has link connectivity
Sun May  1 19:24:15 2022 daemon.notice netifd: Interface 'nwi_mesh0' is setting up now
Sun May  1 19:24:16 2022 kern.info kernel: [ 5588.052875] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready
Sun May  1 19:24:16 2022 kern.info kernel: [ 5588.221508] batman_adv: bat0: Adding interface: mesh0
Sun May  1 19:24:16 2022 kern.info kernel: [ 5588.226845] batman_adv: bat0: Interface activated: mesh0
Sun May  1 19:24:16 2022 daemon.notice netifd: Interface 'nwi_mesh0' is now up

Just an update ,
Created image with the packages outlined above, have a 5ghz mesh up and working, will experiment more,

Thanks for all the help

So if you have the -CT version it is compatible with 802.11s. So it was like I said.

Yes your correct I created a new image with all dependencies installed, and ath10k-smallbuffers, and it working fine, have two nodes working with 5G mesh ,going to try get the 2g mesh working as well.

Cheers

1 Like

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