Hi, I've implemented the failover functionality for babel (package
babeld-auto-gw-mode) and Amuza contributed with testing.
The pull: request
I don't know if everyone know that as per our developer "guidelines"
LibreMesh repository requires at least 2 approved reviews to be able to merge a pull
request. I invite all those interested to collaborate by making a review :)
Best!
SAn
On 12/1/20 7:44 AM, 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?
Hi Amuza!
To my understanding there will be no switch at all.
This has been discussed here [1] but it was not implemented.
Hi Ilario,
Thank you very much for all this very relevant information. I am
completely astonished, as in my case that was a key feature of
LibreMesh. I am involved in a project to share Internet among neighbours
who know almost nothing about networking. Lacking that feature breaks
the project. Well, and somehow my conception of LibreMesh.
This feature was present in the previous releases
for BMX6 [2] (and BMX7
[3]) something similar is present for Batman-adv [4] (no idea in which
case this makes sense, as seems that "Batman-adv only" networks are not
supported [5]).
All these old packages used the watchping package for checking internet
connection.
Now we have the check-internet script which is much more reliable [6].
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 [7] 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 [8]).
Unfortunately I don't understand some technical things there.
I don't know what to do now. I really did not expect this feature could
be gone. I guess I would need some kind of step-by-step guide with more
detailed explanations to fix this. But I'm not sure if that will be
possible or worth it, so I guess the easiest thing for me now it is to
go back to LiMe 17.06 or 16.07.
libremesh.org website has 17.06 as its latest official release, however
the compiling instructions are for newer versions, and the chef is not
there any more, so how could I customise 17.06 so that it contains my
network configuration?
I agree that this feature would be verrrrry
useful.
It feels good to read that! Thank you!
We could continue
the discussion on the issue [1].
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users