My batman-adv mesh has 2x Linksys MR8300 and 2x TP-Link TL-WR902AC v3. The mesh runs on a 5G band, and is WPA3 encrypted. All nodes run OpenWRT 21.02.3.
After upgrading one of the TL-WR902AC's to 22.03.0 with sysupgrade (i.e. no settings changed), this node can no longer ping other nodes in the mesh, and the other way around is also no longer working (this is 'batman ping', i.e. layer 2). The nodes do 'see' each other, however, they show up in each other's neighbour list. If I downgrade (again with sysupgrade, no settings changed) back to 21.02.3 everything starts working again.
Does anyone have a hint what direction to look to get the TL-WR902AC connecting to the mesh on 22.03?
What I've tried:
use wpad-mesh-openssl instead of wpad-mesh-wolfssl; no difference
install 22.03 on an old Archer C7; this connects to the mesh fine
Issues I'm aware of, but don't think are the cause:
the encryption of the mesh shows up as 'none' on the TL-WR902AC, but it also shows up as 'none' on the Archer C7, and that one is working, so I think this is merely cosmetic (on the 21.02 nodes it shows up as 'WPA3 SAE (CCMP)', so this looks perhaps like a glitch in 22.03)
the transmit power of the 5G radio on the TL-WR902AC is low (10-11 dBm), but 21.02 is working with the same transmit power
I can fairly easily switch between 21.02 and 22.03 on the TL-WR902AC to extract data, so if that's required for a better insight in the problem, please let me know.
Thanks for taking your time to look into this. Let me start with that the issue seems to have been solved by upgrading to 22.03-SNAPSHOT, r19737-7c459ac1d5.
But to answer your question, I build my OpenWrt images with imagebuilder with the mesh packages already baked in; then I use sysupgrade to quickly install those images.
For the various images, the installed versions of the mesh software are:
OpenWrt 21.02.3, r16554-1d4dea6d4f:
# opkg list-installed | grep bat
batctl-full - 2021.1-2
kmod-batman-adv - 5.4.188+2021.1-7
# batctl p e8:9f:80:<redacted>
PING e8:9f:80:<redacted> (e8:9f:80:<redacted>) 20(48) bytes of data
20 bytes from e8:9f:80:<redacted> icmp_seq=1 ttl=50 time=2.68 ms
OpenWrt 22.03.0, r19685-512e76967f:
# opkg list-installed | grep bat
batctl-full - 2022.0-3
kmod-batman-adv - 5.10.138+2022.0-4
# batctl p e8:9f:80:<redacted>
PING e8:9f:80:<redacted> (e8:9f:80:<redacted>) 20(48) bytes of data
Reply from host e8:9f:80:<redacted> timed out
OpenWrt 22.03-SNAPSHOT, r19737-7c459ac1d5:
# opkg list-installed | grep bat
batctl-full - 2022.0-3
kmod-batman-adv - 5.10.143+2022.0-4
# batctl p e8:9f:80:<redacted>
PING e8:9f:80:<redacted> (e8:9f:80:<redacted>) 20(48) bytes of data
20 bytes from e8:9f:80:<redacted> icmp_seq=1 ttl=50 time=4.33 ms
So at first sight it appears something changed in kmod-batman-adv that made it work again.