BATMAN and 802.11s ARP bug, is it affected?

Hey all,

I installed openwrt on my accesspoints and I will soon be flashing my router with openwrt.
I am fairly new to networking.

According to the documentation there is a bug regarding ARP in the 802.11s protocol in openwrt.
It happens that my topology is such that the bug would affect my setup (see OG bugreport below).
So to create a mesh network I can't use 802.11s by itself. If I use b.a.t.m.a.n. , is it affected by the same bug? The documentation of b.a.t.m.a.n says that it is build on top of 802.11s, therefore I suspect it might be affected.

My questions:

  1. Is B.a.t.m.a.n affected by the bug mentioned?
  2. If I have a central router with openwrt with multiple accesspoints: Do i need to configure b.a.t.m.a.n on all my devices or only on my router?

OG Bugreport mentioned in the documentation: BUG Report: 802.11s Mesh (V19.07.4) - #4 by rob.clark56

Thanks for your time in advance,

Those reports never say which hardware / driver is in use, or for the person having a problem with mesh if it is a plain 802.11s mesh or under BATMAN. (My understanding is that BATMAN encapsulates every packet, making an ARP no different from anything else to the radio).

So with details so lacking, no one has tried to replicate the problem.

As far as your questions: 1 would be probably not, and 2 is that since BATMAN is handling the network routing, every node in the mesh needs to be running a compatible version of BATMAN in order to join. Typically the nodes will run regular APs for the end users such as smartphones and laptops. It is very rare for an endpoint device to directly be a mesh node.

Sometimes my chromecast discovery also gets unreliable , dont know if its the bug at root cause?