Re: Gateway shut down detection takes too time from other nodes

I think I have a similar use-case as the original poster and ran into the same problem. 

Let me try to explain:

- Given a mesh network where each node is assigned a *static IP*.
- In the mesh network there are some nodes acting as a Gateway.
- The other nodes in the mesh are clients.
- Using BATMAN-V

Each client node has a script running, when it detects "batctl gwl" to elect another gateway, the script will set the gateway's IP-address as default route: "ip route replace default via $gateway_ip dev bat0".

Now whenever a mesh-gateway is turned off, it will take 200 seconds before it is removed from the originators and only then "batctl gwl" will elect another gateway. This results in some client nodes have no internet for 200 seconds.

So far, I haven't been able to get batman-adv (using batctl) to switch to another gateway sooner, e.g. after 10 or 20 seconds.


Using DHCP is not an option in my use-case.

Is there somehow a way to reduce the 200 seconds? Possibly by switching to BATMAN-IV?

Regards, Martin