Am Di., 13. Apr. 2021 um 14:03 Uhr schrieb Sven Eckelmann sven@narfation.org:
Please avoid the ath10k-ct firmware. And for ath10k, please make sure to set mesh_fwding=0 on the mesh(point) interface.
This is true for Wave-1 chipsets (QCA98xx) but Wave-2 Chipsets (QCA99xx) needs the ath10-ct firmware to get 802.11s running.
Haven't got stable results with BATMAN V in a home mesh environment. Nodes could ping each other via batctl ping but IP ping often failed. Maybe some issues of mesh routing when many routes to the same target had nearly the same link speeds? I'm using a dense setup of many routers, so every router is seeing at least 2-3 neighbours. The preferred routes (marked with a [*] in batctl o ?) switched quite often. How is the BATMAN V metric affected by link quality & hop count?
Regards, Andi