I've just tried out running batman-adv over 802.11s (unrouted) mesh as an alternative to trunking VLANs over L2 GRE tunnels. When running the BATMAN_V routing option, I see:
- Relatively long times until a host is found by ping or the like (3-5 seconds)
- Loss of connectivity even once established
sudo batctl o does show the nodes "checking in" within the expected 1-second period.
I strongly believe that the mesh connectivity is good, as I can quickly connect over a parallel (routed) 802.11s mesh on the same radios.
Switching back to the default BATMAN_IV routing protocol seems to have much better results, with the initial ping generally returned, or, at worst the second.
/etc/config/batman-adv is default
Is this a "known issue" with BATMAN_V?
Edit: The "discovery" process, while better with BATMAN_IV, seems to be unreliable, especially from wired hosts to on-mesh hosts. It "feels like" it is poor for "quiet" interfaces, such as those on my management VLAN.
config interface 'nwi_mesh1' option ifname 'mesh1' option mtu '1532' option proto 'batadv' # option routing_algo 'BATMAN_V' option mesh 'bat0'