On 11/30/20 1:55 PM, amuza wrote:
A node is connected to Internet gateway A, but it also
has access to
Internet gateway B. If gateway A fails, how long does it take to start
using gateway B?
To my understanding there will be no switch at all.
This has been discussed here  but it was not implemented.
This feature was present in the previous releases for BMX6  (and BMX7
) something similar is present for Batman-adv  (no idea in which
case this makes sense, as seems that "Batman-adv only" networks are not
All these old packages used the watchping package for checking internet
Now we have the check-internet script which is much more reliable .
I am not sure how a "babeld-auto-gw" could communicate to Babeld to stop
sharing the default (0.0.0.0/0) route.
I can think of two ways:
1) edit the kernel route (e.g. increasing the metric and setting
"reflect-kernel-metric true" Babeld option) and then send a SIGUSR2 to
Babeld process (see  for Babeld manual)
2) edit the Babeld configuration via UCI for stopping the distribution
of the default route and instruct Babeld to reload configuration (the
init script will automatically do so once the uci configuration is
edited and reload_config is executed, otherwise it can be done manually
with /etc/init.d/babeld reload ).
I agree that this feature would be verrrrry useful. We could continue
the discussion on the issue .