30 Nov
2020
30 Nov
'20
12:55 p.m.
Hi,
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?
30 Nov
30 Nov
5:39 p.m.
amuza:
Hi,
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?
I have been waiting for an hour or so and it does not work.
All my tests are done with LiMe based on 19.07.3
The router reaches Internet gateway A through an ethernet cable plugged
in its WAN port. Then I disconnect Gateway A from the Internet and the
router cannot access the Internet any more, as expected. But it does not
failover to Internet Gateway B, which is wirelessly available through
another node in the community. Not even after a while.
Only rebooting the router and unplugging the cable from its WAN port,
makes the router connect to gateway B. I had to do the two things to
make it work.
It looks like a bug.
I think I did the same test few years ago and the router could
automatically find an alternative working Internet gateway in the
community without rebooting or unplugging any cable (maybe it took a
couple of minutes or so, can't remember, but it did it without human
intervention).
I'm also playing with other routers and they are not wirelessly sharing
the Internet connection, and rebooting does not help. But I must leave
now, can't investigate further.
Anyone has done these kind of tests on LiMe based on 19.07.3?
Should I open an issue for this?
I guess I will be able to resume the tests in a week or so.
6:06 p.m.
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?
Hi Amuza!
To my understanding there will be no switch at all.
This has been discussed here [1] but it was not implemented.
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]).
I agree that this feature would be verrrrry useful. We could continue
the discussion on the issue [1].
Ciao!
Ilario
[1]:
https://github.com/libremesh/lime-packages/issues/93
[2]:
https://github.com/libremesh/lime-packages/tree/master/packages/bmx6-auto-g…
[3]:
https://github.com/libremesh/lime-packages/tree/master/packages/bmx7-auto-g…
[4]:
https://github.com/libremesh/lime-packages/tree/master/packages/batman-adv-…
[5]:
https://github.com/libremesh/lime-packages/issues/666
https://github.com/libremesh/lime-packages/issues/468
[6]:
https://github.com/libremesh/lime-packages/tree/master/packages/check-inter…
[7]:
https://www.irif.fr/~jch/software/babel/babeld.html
[8]:
https://openwrt.org/docs/guide-developer/procd-init-scripts#specifying_trig…
--
Ilario
iochesonome(a)gmail.com
ilario(a)sindominio.net
1 Dec
1 Dec
1:43 a.m.
Great info Ilario, I added a comment on babel-pinger (that I've found a couple of
months ago) in https://github.com/libremesh/lime-packages/issues/93
SAn
On 11/30/20 3:06 PM, Ilario Gelmetti wrote:
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?
Hi Amuza!
To my understanding there will be no switch at all.
This has been discussed here [1] but it was not implemented.
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]).
I agree that this feature would be verrrrry useful. We could continue
the discussion on the issue [1].
Ciao!
Ilario
[1]:
https://github.com/libremesh/lime-packages/issues/93
[2]:
https://github.com/libremesh/lime-packages/tree/master/packages/bmx6-auto-g…
[3]:
https://github.com/libremesh/lime-packages/tree/master/packages/bmx7-auto-g…
[4]:
https://github.com/libremesh/lime-packages/tree/master/packages/batman-adv-…
[5]:
https://github.com/libremesh/lime-packages/issues/666
https://github.com/libremesh/lime-packages/issues/468
[6]:
https://github.com/libremesh/lime-packages/tree/master/packages/check-inter…
[7]:
https://www.irif.fr/~jch/software/babel/babeld.html
[8]:
https://openwrt.org/docs/guide-developer/procd-init-scripts#specifying_trig…
10:44 a.m.
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.
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].
Ciao!
Ilario
[1]:
https://github.com/libremesh/lime-packages/issues/93
[2]:
https://github.com/libremesh/lime-packages/tree/master/packages/bmx6-auto-g…
[3]:
https://github.com/libremesh/lime-packages/tree/master/packages/bmx7-auto-g…
[4]:
https://github.com/libremesh/lime-packages/tree/master/packages/batman-adv-…
[5]:
https://github.com/libremesh/lime-packages/issues/666
https://github.com/libremesh/lime-packages/issues/468
[6]:
https://github.com/libremesh/lime-packages/tree/master/packages/check-inter…
[7]:
https://www.irif.fr/~jch/software/babel/babeld.html
[8]:
https://openwrt.org/docs/guide-developer/procd-init-scripts#specifying_trig…
12:40 p.m.
Hi Amuza,
On December 1, 2020 7:44:00 AM GMT-03:00, amuza <amuza(a)riseup.net> wrote:
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 is a feature that is very high in our todo list for the babel configuration. It is a
feature that is needed in most networks. It is not implemented yet because lack of time
not because it is not important.
The current software still supports BMX6 that has this feature. You can build a firmware
with BMX6, selecting lime-proto-bmx6 and the BMX6 protocol may do it. You should deselect
babel.
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
> 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.
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].
Ciao!
Ilario
[1]:
https://github.com/libremesh/lime-packages/issues/93
[2]:
https://github.com/libremesh/lime-packages/tree/master/packages/bmx6-auto-g…
[3]:
https://github.com/libremesh/lime-packages/tree/master/packages/bmx7-auto-g…
[4]:
https://github.com/libremesh/lime-packages/tree/master/packages/batman-adv-…
[5]:
https://github.com/libremesh/lime-packages/issues/666
https://github.com/libremesh/lime-packages/issues/468
[6]:
https://github.com/libremesh/lime-packages/tree/master/packages/check-inter…
https://openwrt.org/docs/guide-developer/procd-init-scripts#specifying_trig…
1:17 p.m.
SAn:
The current software still supports BMX6 that has this feature. You can build a firmware
with BMX6, selecting lime-proto-bmx6 and the BMX6 protocol may do it. You should deselect
babel.
Wow, that sounds very easy!! I will do so. Thank you very much!!
Hi Amuza,
On December 1, 2020 7:44:00 AM GMT-03:00, amuza <amuza(a)riseup.net> wrote:
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 is a feature that is very high in our todo list for the babel configuration. It is a
feature that is needed in most networks. It is not implemented yet because lack of time
not because it is not important.
Hi SAn,
It's great to read that, thank you!
> 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.
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].
>>
>
>> Ciao!
>> Ilario
>>
>> [1]:
>> https://github.com/libremesh/lime-packages/issues/93
>> [2]:
>>
> https://github.com/libremesh/lime-packages/tree/master/packages/bmx6-auto-g…
>> [3]:
>>
> https://github.com/libremesh/lime-packages/tree/master/packages/bmx7-auto-g…
>> [4]:
>>
>
https://github.com/libremesh/lime-packages/tree/master/packages/batman-adv-…
>> [5]:
>> https://github.com/libremesh/lime-packages/issues/666
>> https://github.com/libremesh/lime-packages/issues/468
>> [6]:
>>
> https://github.com/libremesh/lime-packages/tree/master/packages/check-inter…
>> [7]:
>> https://www.irif.fr/~jch/software/babel/babeld.html
>> [8]:
>>
> https://openwrt.org/docs/guide-developer/procd-init-scripts#specifying_trig…
>>
> _______________________________________________
> lime-users mailing list
> lime-users(a)lists.libremesh.org
> https://lists.libremesh.org/mailman/listinfo/lime-users
1:19 p.m.
On December 1, 2020 10:17:00 AM GMT-03:00, amuza <amuza(a)riseup.net> wrote:
SAn:
configuration.
It is a feature that is needed in most networks. It is
not implemented yet because lack of time not because it is not
important.
Hi SAn,
It's great to read that, thank you!
> The current software still supports
BMX6 that has this feature. You
can build a firmware with BMX6, selecting lime-proto-bmx6 and the BMX6
protocol may do it. You should deselect babel.
Wow, that sounds very easy!! I will do so. Thank you very much!!
I did not build a BMX6 firmware for at least one year, so, fingerscrossed. Good luck!
Hi Amuza,
On December 1, 2020 7:44:00 AM GMT-03:00, amuza <amuza(a)riseup.net>
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 is a feature that is very high in our todo list for the babel >
>> 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].
>>
>
>> Ciao!
>> Ilario
>>
>> [1]:
>> https://github.com/libremesh/lime-packages/issues/93
>> [2]:
>>
>
https://github.com/libremesh/lime-packages/tree/master/packages/bmx6-auto-g…
>> [3]:
>>
>
https://github.com/libremesh/lime-packages/tree/master/packages/bmx7-auto-g…
>> [4]:
>>
>
https://github.com/libremesh/lime-packages/tree/master/packages/batman-adv-…
>> [5]:
>> https://github.com/libremesh/lime-packages/issues/666
>> https://github.com/libremesh/lime-packages/issues/468
>> [6]:
>>
>
https://github.com/libremesh/lime-packages/tree/master/packages/check-inter…
>> [7]:
>> https://www.irif.fr/~jch/software/babel/babeld.html
>> [8]:
>>
>
https://openwrt.org/docs/guide-developer/procd-init-scripts#specifying_trig…
>>>
>> _______________________________________________
>> lime-users mailing list
>> lime-users(a)lists.libremesh.org
>> https://lists.libremesh.org/mailman/listinfo/lime-users
1:22 p.m.
The current
software still supports BMX6 that has this feature. You can build a firmware with BMX6,
selecting lime-proto-bmx6 and the BMX6 protocol may do it. You should deselect babel.
Wow, that sounds very easy!! I will do so. Thank you very much!!
>>
1:32 p.m.
The current software still supports BMX6 that has this feature. You
can build a
firmware with BMX6, selecting lime-proto-bmx6 and the BMX6
protocol may do it. You should deselect babel.
3 Dec
3 Dec
8:12 p.m.
Hi,
In order to have an Internet-sharing LibreMesh, I have removed
lime-proto-babeld and shared-state-babeld_hosts
And regarding BMX6, I have added bmx6 and lime-proto-bmx6.
By doing a search in menuconfig (/) I have also found the following BMX6
items, do you think I also need any of them?
- bmx6-auto-gw-mode (this one sounds good to me)
- bmx6-json
- bmx6-sms
- bmx6-table
- bmx6-uci-config
- luci-app-bmx6
- luci-lib-libremap-bmx6
- prometheus-node-exporter-lua-bmx6
- ubus-lime-bmx6
Thank you
9:11 p.m.
Hi!
On 12/1/20 10:22 AM, amuza wrote:
>> The current software still supports BMX6 that has this feature. You can build a
firmware with BMX6, selecting lime-proto-bmx6 and the BMX6 protocol may do it. You should
deselect babel.
There are multiple reasons. In my opinion the most important is that the babel protocol is
now an IETF standard. Also important is that babel the protocol and babeld the
implementation are being supported/maintained. BMX6 development stalled and is not
maintained (AFAIK) long time ago and we had some problems with the implementation so it
was difficult "to promote" it as the default libremesh protocol.
Anyway the idea behind libremesh is that multiple protocols can be selected/used, so BMX6
and BMX7 and other protocols are supported at least as there are community using them to
report bugs and help fix them.
SAn
9:14 p.m.
Hi
On 12/3/20 5:12 PM, amuza wrote:
Hi,
In order to have an Internet-sharing LibreMesh, I have removed
lime-proto-babeld and shared-state-babeld_hosts
And regarding BMX6, I have added bmx6 and lime-proto-bmx6.
By doing a search in menuconfig (/) I have also found the following BMX6
items, do you think I also need any of them?
- bmx6-auto-gw-mode (this one sounds good to me)
- bmx6-json
- bmx6-sms
- bmx6-table
- bmx6-uci-config
- luci-app-bmx6
- luci-lib-libremap-bmx6
- prometheus-node-exporter-lua-bmx6
- ubus-lime-bmx6
I would select bmx6-auto-gw-mode and depending if you are using the lime app or luci
select ubus-lime-bmx6 for the lime app and luci-app-bmx6 for luci.
Good luck!
9:21 p.m.
SAn:
Hi
On 12/3/20 5:12 PM, amuza wrote:
Thank you SAn!
Hi,
In order to have an Internet-sharing LibreMesh, I have removed
lime-proto-babeld and shared-state-babeld_hosts
And regarding BMX6, I have added bmx6 and lime-proto-bmx6.
By doing a search in menuconfig (/) I have also found the following BMX6
items, do you think I also need any of them?
- bmx6-auto-gw-mode (this one sounds good to me)
- bmx6-json
- bmx6-sms
- bmx6-table
- bmx6-uci-config
- luci-app-bmx6
- luci-lib-libremap-bmx6
- prometheus-node-exporter-lua-bmx6
- ubus-lime-bmx6
I would select bmx6-auto-gw-mode and depending if you are using the lime app or luci
select ubus-lime-bmx6 for the lime app and luci-app-bmx6 for luci.
Good luck!
9:28 p.m.
SAn:
Hi!
On 12/1/20 10:22 AM, amuza wrote:
Nice explanation, thank you. I will migrate to Babel once this
Internet-sharing thing is fixed.
>> The current software still supports BMX6 that has this feature. You can build a
firmware with BMX6, selecting lime-proto-bmx6 and the BMX6 protocol may do it. You should
deselect babel.
There are multiple reasons. In my opinion the most important is that the babel protocol
is now an IETF standard. Also important is that babel the protocol and babeld the
implementation are being supported/maintained. BMX6 development stalled and is not
maintained (AFAIK) long time ago and we had some problems with the implementation so it
was difficult "to promote" it as the default libremesh protocol.
Anyway the idea behind libremesh is that multiple protocols can be selected/used, so BMX6
and BMX7 and other protocols are supported at least as there are community using them to
report bugs and help fix them.
SAn
4 Dec
4 Dec
2:30 a.m.
In our case I think at some point we would like to switch to babel, and I
did not know that this is something not present in babel. I copied the
answer of Ilario to my notes, but keeping it simple: can I have more simple
information to track this issue (which I hope includes all the relevant
details), and then I will subscribe to that issue.
In Barcelona we are running bmx6 since years. A subnetwork of it we are
running a pure bmx6 network based on openwrt, and it is a little bit
unstable (daemon crashes), but works fine. I hope soon we can go for the
latest bmx6 version in the whole network (migrations are painful), because
recently we discovered that openwrt packages was using an old and
memleaked version of bmx6 (!!)
https://github.com/openwrt-routing/packages/issues/573
On Thu, Dec 3, 2020 at 10:28 PM amuza <amuza(a)riseup.net> wrote:
SAn:
Hi!
On 12/1/20 10:22 AM, amuza wrote:
>
>>> The current software still supports BMX6 that has this feature. You
can build a firmware with BMX6, selecting lime-proto-bmx6 and the BMX6
protocol may do it. You should deselect babel.
There are multiple reasons. In my opinion the most important is that the
babel
protocol is now an IETF standard. Also important is that babel the
protocol and babeld the implementation are being supported/maintained. BMX6
development stalled and is not maintained (AFAIK) long time ago and we had
some problems with the implementation so it was difficult "to promote" it
as the default libremesh protocol.
Anyway the idea behind libremesh is that multiple
protocols can be
selected/used, so BMX6 and BMX7 and other protocols are supported
at least
as there are community using them to report bugs and help fix them.
SAn
Nice explanation, thank you. I will migrate to Babel once this
Internet-sharing thing is fixed.
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users 
4:42 p.m.
Hi all,
till this thread I believed that babeld could do this change of Internet
Connection. And I "think" I saw this as a feature on the website - and was
one of the points why I started using libremesh.
As I remember there were als mentions of bmx6 and bmx7 so this could be the
reason for this misunderstanding. -> I think it came from here:
https://libremesh.org/howitworks.html
There is still bmx as layer 3 routing protocol...
Maybe the documentation should be changed?
Regards,
Andy
Am Fr., 4. Dez. 2020 um 03:30 Uhr schrieb guifipedro <guifipedro(a)gmail.com>om>:
In our case I think at some point we would like to
switch to babel, and I
did not know that this is something not present in babel. I copied the
answer of Ilario to my notes, but keeping it simple: can I have more simple
information to track this issue (which I hope includes all the relevant
details), and then I will subscribe to that issue.
In Barcelona we are running bmx6 since years. A subnetwork of it we are
running a pure bmx6 network based on openwrt, and it is a little bit
unstable (daemon crashes), but works fine. I hope soon we can go for the
latest bmx6 version in the whole network (migrations are painful), because
recently we discovered that openwrt packages was using an old and
memleaked version of bmx6 (!!)
https://github.com/openwrt-routing/packages/issues/573
On Thu, Dec 3, 2020 at 10:28 PM amuza <amuza(a)riseup.net> wrote:
SAn:
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users Hi!
On 12/1/20 10:22 AM, amuza wrote:
>
>>> The current software still supports BMX6 that has this feature. You
can build a firmware with BMX6, selecting lime-proto-bmx6 and the BMX6
protocol may do it. You should deselect babel.
There are multiple reasons. In my opinion the most important is that
the babel
protocol is now an IETF standard. Also important is that babel
the protocol and babeld the implementation are being supported/maintained.
BMX6 development stalled and is not maintained (AFAIK) long time ago and we
had some problems with the implementation so it was difficult "to promote"
it as the default libremesh protocol.
Anyway the idea behind libremesh is that multiple
protocols can be
selected/used, so BMX6 and BMX7 and other protocols are supported
at least
as there are community using them to report bugs and help fix them.
SAn
Nice explanation, thank you. I will migrate to Babel once this
Internet-sharing thing is fixed.
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
7:48 p.m.
On 12/4/20 5:42 PM, Andy Schopf wrote:
till this thread I believed that babeld could do this
change of Internet
Connection.
Babeld takes the routes from the kernel and distrubutes them with a
modified metric based on the quality of the links, if I got it correctly.
I also think that this feature is super needed in LibreMesh but I have
no idea if anyone is working on this.
At this point seems that the next release 20.09 will be released this
week and that it will not include this feature.
If someone develops it, the feature could be included in 20.09.1 :D
Some discussion is going on here:
https://github.com/libremesh/lime-packages/issues/93
And some more issues are prioritized here:
https://github.com/orgs/libremesh/projects/2
And I "think" I saw this as a feature on the
website - and
was one of the points why I started using libremesh.
As I remember there were als mentions of bmx6 and bmx7 so this could be
the reason for this misunderstanding. -> I think it came from here:
https://libremesh.org/howitworks.html
<https://libremesh.org/howitworks.html>
There is still bmx as layer 3 routing protocol...
Maybe the documentation should be changed?
Yep, the documentation is updated to the last stable release 17.06
(mostly, SAn and others updated a lot of documentation in the Spanish
version of the website (there's a button for changing language on the
top of the menu)), any help in updating the website is welcome!
Each webpage in the website has, on the top right, a "Edit this page"
button :)
Ciao!
Ilario
5 Dec
5 Dec
8:14 p.m.
SAn:
Hi
On 12/3/20 5:12 PM, amuza wrote:
I tested it. It works ok with BMX6. But not optimally.
I have Router A, B and C with LiMe based on OpenWRT 19.07 with BMX6, no
Babel. They are connected like shown below:
ISP-A ISP-C
| |
RouterA <--> RouterB <--> RouterC
RouterA is connected to ISP-A.
RouterC is connected to ISP-C.
Router-B can reach the Internet via both ISP-A and ISP-C without a
problem, switching gateways automatically when needed.
However, if ISP-A fails, RouterA won't reach the Internet through ISP-C
automatically: it will need a manual reboot :(
And so, the same applies at the other end: if ISP-C fails, RouterC won't
reach the Internet though ISP-A unless you give it a manual reboot.
Hi,
In order to have an Internet-sharing LibreMesh, I have removed
lime-proto-babeld and shared-state-babeld_hosts
And regarding BMX6, I have added bmx6 and lime-proto-bmx6.
By doing a search in menuconfig (/) I have also found the following BMX6
items, do you think I also need any of them?
- bmx6-auto-gw-mode (this one sounds good to me)
- bmx6-json
- bmx6-sms
- bmx6-table
- bmx6-uci-config
- luci-app-bmx6
- luci-lib-libremap-bmx6
- prometheus-node-exporter-lua-bmx6
- ubus-lime-bmx6
I would select bmx6-auto-gw-mode and depending if you are using the lime app or luci
select ubus-lime-bmx6 for the lime app and luci-app-bmx6 for luci.
Good luck!
7 Dec
7 Dec
5:37 p.m.
I tested it. It works ok with BMX6. But not
optimally.
I have Router A, B and C with LiMe based on OpenWRT 19.07 with BMX6, no
Babel. They are connected like shown below:
ISP-A ISP-C
| |
RouterA <--> RouterB <--> RouterC
RouterA is connected to ISP-A.
RouterC is connected to ISP-C.
Router-B can reach the Internet via both ISP-A and ISP-C without a
problem, switching gateways automatically when needed.
However, if ISP-A fails, RouterA won't reach the Internet through ISP-C
automatically: it will need a manual reboot :(
And so, the same applies at the other end: if ISP-C fails, RouterC won't
reach the Internet though ISP-A unless you give it a manual reboot.
I forgot to say that RouterA is connected to ISP-A through its WAN
ethernet port, and RouterC is connected to ISP-C through its WAN
ethernet port.
I have done again the same test as described above, but now with Babel.
Their behaviour is exactly the same as with BMX6.
So, with these results, I am coming back to official Babel.
By the way, Router B needs some time to automatically switch over to a
working Internet gateway, maybe something like 10 minutes, not sure.
Just informing, I think such amount of time is ok.
I would like to get informed if there is a fix on this issue, but I am
not sure whether issue 93 is really dealing with it or with a different
topic, as their initial descriptions explain other problems.
https://github.com/libremesh/lime-packages/issues/93
Will issue 93 deal with the problems or RouterA and RouterC?
Otherwise I can open a new issue.
Thank you
11:27 p.m.
amuza:
Just in case I was not clear: If a router stops reaching the Internet
through its WAN port, it will not be able to find an alternative route
unless you manually reboot it. And that happens with Babel and with BMX6.
I tested it. It works ok with BMX6. But not
optimally.
I have Router A, B and C with LiMe based on OpenWRT 19.07 with BMX6, no
Babel. They are connected like shown below:
ISP-A ISP-C
| |
RouterA <--> RouterB <--> RouterC
RouterA is connected to ISP-A.
RouterC is connected to ISP-C.
Router-B can reach the Internet via both ISP-A and ISP-C without a
problem, switching gateways automatically when needed.
However, if ISP-A fails, RouterA won't reach the Internet through ISP-C
automatically: it will need a manual reboot :(
And so, the same applies at the other end: if ISP-C fails, RouterC won't
reach the Internet though ISP-A unless you give it a manual reboot.
I forgot to say that RouterA is connected to ISP-A through its WAN
ethernet port, and RouterC is connected to ISP-C through its WAN
ethernet port.
I have done again the same test as described above, but now with Babel.
Their behaviour is exactly the same as with BMX6.
So, with these results, I am coming back to official Babel.
By the way, Router B needs some time to automatically switch over to a
working Internet gateway, maybe something like 10 minutes, not sure.
Just informing, I think such amount of time is ok.
I would like to get informed if there is a fix on this issue, but I am
not sure whether issue 93 is really dealing with it or with a different
topic, as their initial descriptions explain other problems.
https://github.com/libremesh/lime-packages/issues/93
Will issue 93 deal with the problems or RouterA and RouterC?
Otherwise I can open a new issue.
Thank you
11:52 p.m.
Hi!
On 12/7/20 8:27 PM, amuza wrote:
amuza:
Just in case I was not clear: If a router stops reaching the Internet
through its WAN port, it will not be able to find an alternative route
unless you manually reboot it. And that happens with Babel and with BMX6.
Are you using bmx6-auto-gw-mode ? Maybe it is not working or watchping is not correctly
configured?
How are you "removing internet" from the gateways?
I tested it. It works ok with BMX6. But not
optimally.
I have Router A, B and C with LiMe based on OpenWRT 19.07 with BMX6, no
Babel. They are connected like shown below:
ISP-A ISP-C
| |
RouterA <--> RouterB <--> RouterC
RouterA is connected to ISP-A.
RouterC is connected to ISP-C.
Router-B can reach the Internet via both ISP-A and ISP-C without a
problem, switching gateways automatically when needed.
However, if ISP-A fails, RouterA won't reach the Internet through ISP-C
automatically: it will need a manual reboot :(
And so, the same applies at the other end: if ISP-C fails, RouterC won't
reach the Internet though ISP-A unless you give it a manual reboot.
I forgot to say that RouterA is connected to ISP-A through its WAN
ethernet port, and RouterC is connected to ISP-C through its WAN
ethernet port.
I have done again the same test as described above, but now with Babel.
Their behaviour is exactly the same as with BMX6.
So, with these results, I am coming back to official Babel.
By the way, Router B needs some time to automatically switch over to a
working Internet gateway, maybe something like 10 minutes, not sure.
Just informing, I think such amount of time is ok.
I would like to get informed if there is a fix on this issue, but I am
not sure whether issue 93 is really dealing with it or with a different
topic, as their initial descriptions explain other problems.
https://github.com/libremesh/lime-packages/issues/93
Will issue 93 deal with the problems or RouterA and RouterC?
Otherwise I can open a new issue.
Thank you
8 Dec
8 Dec
11:38 p.m.
SAn:
Hi!
Hey!
On 12/7/20 8:27 PM, amuza wrote:
Yes, when testing LiMe with BMX6, it included bmx6-auto-gw-mode.
amuza:
Just in case I was not clear: If a router stops reaching the Internet
through its WAN port, it will not be able to find an alternative route
unless you manually reboot it. And that happens with Babel and with BMX6.
Are you using bmx6-auto-gw-mode ? I tested it. It works ok with BMX6. But not
optimally.
I have Router A, B and C with LiMe based on OpenWRT 19.07 with BMX6, no
Babel. They are connected like shown below:
ISP-A ISP-C
| |
RouterA <--> RouterB <--> RouterC
RouterA is connected to ISP-A.
RouterC is connected to ISP-C.
Router-B can reach the Internet via both ISP-A and ISP-C without a
problem, switching gateways automatically when needed.
However, if ISP-A fails, RouterA won't reach the Internet through ISP-C
automatically: it will need a manual reboot :(
And so, the same applies at the other end: if ISP-C fails, RouterC won't
reach the Internet though ISP-A unless you give it a manual reboot.
I forgot to say that RouterA is connected to ISP-A through its WAN
ethernet port, and RouterC is connected to ISP-C through its WAN
ethernet port.
I have done again the same test as described above, but now with Babel.
Their behaviour is exactly the same as with BMX6.
So, with these results, I am coming back to official Babel.
By the way, Router B needs some time to automatically switch over to a
working Internet gateway, maybe something like 10 minutes, not sure.
Just informing, I think such amount of time is ok.
I would like to get informed if there is a fix on this issue, but I am
not sure whether issue 93 is really dealing with it or with a different
topic, as their initial descriptions explain other problems.
https://github.com/libremesh/lime-packages/issues/93
Will issue 93 deal with the problems or RouterA and RouterC?
Otherwise I can open a new issue.
Thank you
Maybe it is not working or watchping is not correctly
configured?
I don't know.
How do I know if it is working or if watchping is not correctly configured?
How are you "removing internet" from the
gateways?
I did not touch the LiMe router, I kept active its WAN connection to the
ISP. I just prevented the "ISP router" from reaching the Internet.
But I think I also tested it by physically pulling out the cable from
LiMe router's WAN port and saw no difference. There is no failover
unless it is manually rebooted.
9 Dec
9 Dec
9:57 a.m.
Hi Amuza!
Some comments in line:
On 12/5/20 9:14 PM, amuza wrote:
I tested it. It works ok with BMX6. But not
optimally.
I have Router A, B and C with LiMe based on OpenWRT 19.07 with BMX6, no
Babel. They are connected like shown below:
ISP-A ISP-C
| |
RouterA <--> RouterB <--> RouterC
RouterA is connected to ISP-A.
RouterC is connected to ISP-C.
Router-B can reach the Internet via both ISP-A and ISP-C without a
problem, switching gateways automatically when needed.
However, if ISP-A fails, RouterA won't reach the Internet through ISP-C
automatically: it will need a manual reboot :(
And so, the same applies at the other end: if ISP-C fails, RouterC won't
reach the Internet though ISP-A unless you give it a manual reboot.
This is exactly what bmx6-auto-gw-mode does: when the internet
connection fails the gateway (Router-A or Router-C) stops **announcing
itself as a gateway to the other nodes** (Router-B).
But the gateway node itself (Router-A or Router-C) continues using their
own WAN.
I suppose that this was done so that the gateway node can continue
checking if the WAN starts working again.
So what you're seeing is expected, with bmx6-auto-gw-mode.
With Babeld, as an equivalent feature is missing, the Router-B should
not switch connection when you unplug the telephone/coaxial/fiber cable
from ISP-A or ISP-C (which is the best way to remove the connection, in
my opinion), can you confirm this?
Let's take the example that Router-A loses connection to the internet.
Router-A will stop telling to the rest of the network that internet can
be reached there. But Router-A will still use that WAN for trying
pinging the internet and once the connection is working the ping will
start working again and it will announce the internet availability again.
If we want to have also Router-A switching to use Router-C internet
access while still checking if its own internet access works, we can use
two default routes and play with the metrics (the priority of the two
ways to reach the internet).
The way through Router-C (which works) can have lower priority (i.e.
higher priority) and the way through ISP-A (broken) can be used by ping
with the -I option (forces ping to use a specific interface, this option
is present also in the ping version included in OpenWrt).
Amuza, if we want to improve the watchping package and the
bmx6-auto-gw-mode package it would be useful to open an issue on Github,
can you do it?
For implementing something similar using the check-internet package
(which is much more reliable than ping, as it does not get fooled by
networks blocking ping or by captive portals answering to all the pings)
we should include the full wget or curl packages, check out this comment
for more:
https://github.com/libremesh/lime-packages/issues/93#issuecomment-739014966
Ciao!
Ilario
--
Ilario
iochesonome(a)gmail.com
ilario(a)sindominio.net
10 Dec
10 Dec
12:05 a.m.
Ilario Gelmetti:
Hi Amuza!
Some comments in line:
Hi Ilario!
On 12/5/20 9:14 PM, amuza wrote:
Yes, I agree, that's the correct way to test it. I disconnected the ISP
router from the Internet, but kept the Mesh router properly connected to
the ISP router.
With Babel, RouterB does switch from ISP-A to ISP-C too, as BMX6 does.
I tested it. It works ok with BMX6. But not
optimally.
I have Router A, B and C with LiMe based on OpenWRT 19.07 with BMX6, no
Babel. They are connected like shown below:
ISP-A ISP-C
| |
RouterA <--> RouterB <--> RouterC
RouterA is connected to ISP-A.
RouterC is connected to ISP-C.
Router-B can reach the Internet via both ISP-A and ISP-C without a
problem, switching gateways automatically when needed.
However, if ISP-A fails, RouterA won't reach the Internet through ISP-C
automatically: it will need a manual reboot :(
And so, the same applies at the other end: if ISP-C fails, RouterC won't
reach the Internet though ISP-A unless you give it a manual reboot.
This is exactly what bmx6-auto-gw-mode does: when the internet
connection fails the gateway (Router-A or Router-C) stops **announcing
itself as a gateway to the other nodes** (Router-B).
But the gateway node itself (Router-A or Router-C) continues using their
own WAN.
I suppose that this was done so that the gateway node can continue
checking if the WAN starts working again.
So what you're seeing is expected, with bmx6-auto-gw-mode.
With Babeld, as an equivalent feature is missing, the Router-B should
not switch connection when you unplug the telephone/coaxial/fiber cable
from ISP-A or ISP-C (which is the best way to remove the connection, in
my opinion), can you confirm this?
Let's take the example that Router-A loses connection to the internet.
Router-A will stop telling to the rest of the network that internet can
be reached there. But Router-A will still use that WAN for trying
pinging the internet and once the connection is working the ping will
start working again and it will announce the internet availability again.
If we want to have also Router-A switching to use Router-C internet
access while still checking if its own internet access works,
Yes, that would be perfect.
we can use
two default routes and play with the metrics (the priority of the two
ways to reach the internet).
The way through Router-C (which works) can have lower priority(i.e.
higher priority)
I understand, you meant 'lower metrics'.
and the way through ISP-A (broken) can be used by
ping
with the -I option (forces ping to use a specific interface, this option
is present also in the ping version included in OpenWrt).
Amuza, if we want to improve the watchping package and the
bmx6-auto-gw-mode package it would be useful to open an issue on Github,
can you do it?
There you go:
https://github.com/libremesh/lime-packages/issues/822
For implementing something similar using the
check-internet package
(which is much more reliable than ping, as it does not get fooled by
networks blocking ping or by captive portals answering to all the pings)
we should include the full wget or curl packages, check out this comment
for more:
https://github.com/libremesh/lime-packages/issues/93#issuecomment-739014966
Ciao!
Ilario
23 Feb
23 Feb
12:01 a.m.
Hi, I've implemented the failover functionality for babel (package
babeld-auto-gw-mode) and Amuza contributed with testing.
The pull: request https://github.com/libremesh/lime-packages/pull/844
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:
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.
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.
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].
Ciao!
Ilario
[1]:
https://github.com/libremesh/lime-packages/issues/93
[2]:
https://github.com/libremesh/lime-packages/tree/master/packages/bmx6-auto-g…
[3]:
https://github.com/libremesh/lime-packages/tree/master/packages/bmx7-auto-g…
[4]:
https://github.com/libremesh/lime-packages/tree/master/packages/batman-adv-…
[5]:
https://github.com/libremesh/lime-packages/issues/666
https://github.com/libremesh/lime-packages/issues/468
[6]:
https://github.com/libremesh/lime-packages/tree/master/packages/check-inter…
[7]:
https://www.irif.fr/~jch/software/babel/babeld.html
[8]:
https://openwrt.org/docs/guide-developer/procd-init-scripts#specifying_trig…
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
20 Mar
20 Mar
12:03 p.m.
Did this feature go upstream? So anyone compiling official LibreMesh now
gets it?
SAn:
Hi, I've implemented the failover functionality
for babel (package
babeld-auto-gw-mode) and Amuza contributed with testing.
The pull: request https://github.com/libremesh/lime-packages/pull/844
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].
>>
>
>> Ciao!
>> Ilario
>>
>> [1]:
>> https://github.com/libremesh/lime-packages/issues/93
>> [2]:
>>
https://github.com/libremesh/lime-packages/tree/master/packages/bmx6-auto-g…
>>
>> [3]:
>>
https://github.com/libremesh/lime-packages/tree/master/packages/bmx7-auto-g…
>>
>> [4]:
>>
https://github.com/libremesh/lime-packages/tree/master/packages/batman-adv-…
>>
>> [5]:
>> https://github.com/libremesh/lime-packages/issues/666
>> https://github.com/libremesh/lime-packages/issues/468
>> [6]:
>> https://github.com/libremesh/lime-packages/tree/master/packages/check-inter…
>>
>> [7]:
>> https://www.irif.fr/~jch/software/babel/babeld.html
>> [8]:
>> https://openwrt.org/docs/guide-developer/procd-init-scripts#specifying_trig…
>>
>>
> _______________________________________________
> lime-users mailing list
> lime-users(a)lists.libremesh.org
> https://lists.libremesh.org/mailman/listinfo/lime-users
>
7:52 p.m.
Hi! Yes :) You have to select the babeld-auto-gw-mode package
Best!
SAn
On March 20, 2021 9:03:31 AM GMT-03:00, amuza <amuza(a)riseup.net> wrote:
Did this feature go upstream? So anyone compiling
official LibreMesh
now
gets it?
SAn:
Hi, I've implemented the failover
functionality for babel (package
babeld-auto-gw-mode) and Amuza contributed with testing.
The pull: request https://github.com/libremesh/lime-packages/pull/844
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].
>>
>
>> Ciao!
>> Ilario
>>
>> [1]:
>> https://github.com/libremesh/lime-packages/issues/93
>> [2]:
>>
https://github.com/libremesh/lime-packages/tree/master/packages/bmx6-auto-g…
>>
>> [3]:
>>
https://github.com/libremesh/lime-packages/tree/master/packages/bmx7-auto-g…
>>
>> [4]:
>>
https://github.com/libremesh/lime-packages/tree/master/packages/batman-adv-…
>>
>> [5]:
>> https://github.com/libremesh/lime-packages/issues/666
>> https://github.com/libremesh/lime-packages/issues/468
>> [6]:
>>
https://github.com/libremesh/lime-packages/tree/master/packages/check-inter…
>>
>> [7]:
>> https://www.irif.fr/~jch/software/babel/babeld.html
>> [8]:
>>
https://openwrt.org/docs/guide-developer/procd-init-scripts#specifying_trig…
>>>
>>>
>> _______________________________________________
>> lime-users mailing list
>> lime-users(a)lists.libremesh.org
>> https://lists.libremesh.org/mailman/listinfo/lime-users
>>
9:13 p.m.
Cool. Thank you for the reminder!
SAn:
Hi! Yes :) You have to select the babeld-auto-gw-mode
package
Best!
SAn
On March 20, 2021 9:03:31 AM GMT-03:00, amuza <amuza(a)riseup.net> wrote:
> Did this feature go upstream? So anyone compiling official LibreMesh
> now
> gets it?
>
>
>
> SAn:
>> Hi, I've implemented the failover functionality for babel (package
>> babeld-auto-gw-mode) and Amuza contributed with testing.
>>
>> The pull: request https://github.com/libremesh/lime-packages/pull/844
>>
>> 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].
>>>>
>>>
>>>> Ciao!
>>>> Ilario
>>>>
>>>> [1]:
>>>> https://github.com/libremesh/lime-packages/issues/93
>>>> [2]:
>>>>
> https://github.com/libremesh/lime-packages/tree/master/packages/bmx6-auto-g…
>>>>
>>>> [3]:
>>>>
> https://github.com/libremesh/lime-packages/tree/master/packages/bmx7-auto-g…
>>>>
>>>> [4]:
>>>>
>
https://github.com/libremesh/lime-packages/tree/master/packages/batman-adv-…
>>>>
>>>> [5]:
>>>> https://github.com/libremesh/lime-packages/issues/666
>>>> https://github.com/libremesh/lime-packages/issues/468
>>>> [6]:
>>>>
> https://github.com/libremesh/lime-packages/tree/master/packages/check-inter…
>>>>
>>>> [7]:
>>>> https://www.irif.fr/~jch/software/babel/babeld.html
>>>> [8]:
>>>>
> https://openwrt.org/docs/guide-developer/procd-init-scripts#specifying_trig…
>>>>
>>>>
>>> _______________________________________________
>>> lime-users mailing list
>>> lime-users(a)lists.libremesh.org
>>> https://lists.libremesh.org/mailman/listinfo/lime-users
>>>
9:31 p.m.
Shouldn't it be included in the compiling instructions at
https://libremesh.org/development.html ?
amuza:
Cool. Thank you for the reminder!
SAn:
Hi! Yes :) You have to select the
babeld-auto-gw-mode package
Best!
SAn
On March 20, 2021 9:03:31 AM GMT-03:00, amuza <amuza(a)riseup.net> wrote:
> Did this feature go upstream? So anyone compiling official LibreMesh
> now
> gets it?
>
>
>
> SAn:
>> Hi, I've implemented the failover functionality for babel (package
>> babeld-auto-gw-mode) and Amuza contributed with testing.
>>
>> The pull: request https://github.com/libremesh/lime-packages/pull/844
>>
>> 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].
>>>>
>>>
>>>> Ciao!
>>>> Ilario
>>>>
>>>> [1]:
>>>> https://github.com/libremesh/lime-packages/issues/93
>>>> [2]:
>>>>
> https://github.com/libremesh/lime-packages/tree/master/packages/bmx6-auto-g…
>>>>
>>>> [3]:
>>>>
> https://github.com/libremesh/lime-packages/tree/master/packages/bmx7-auto-g…
>>>>
>>>> [4]:
>>>>
>
https://github.com/libremesh/lime-packages/tree/master/packages/batman-adv-…
>>>>
>>>> [5]:
>>>> https://github.com/libremesh/lime-packages/issues/666
>>>> https://github.com/libremesh/lime-packages/issues/468
>>>> [6]:
>>>>
> https://github.com/libremesh/lime-packages/tree/master/packages/check-inter…
>>>>
>>>> [7]:
>>>> https://www.irif.fr/~jch/software/babel/babeld.html
>>>> [8]:
>>>>
> https://openwrt.org/docs/guide-developer/procd-init-scripts#specifying_trig…
>>>>
>>>>
>>> _______________________________________________
>>> lime-users mailing list
>>> lime-users(a)lists.libremesh.org
>>> https://lists.libremesh.org/mailman/listinfo/lime-users
>>>
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
11:02 p.m.
Indeed! Do you want to open a pull request? There is a link in the top right corner.
Thanks!
SAn
On March 20, 2021 6:31:50 PM GMT-03:00, amuza <amuza(a)riseup.net> wrote:
Shouldn't it be included in the compiling
instructions at
https://libremesh.org/development.html ?
amuza:
Cool. Thank you for the reminder!
SAn:
> Hi! Yes :) You have to select the babeld-auto-gw-mode package
>
> Best!
> SAn
>
> On March 20, 2021 9:03:31 AM GMT-03:00, amuza <amuza(a)riseup.net>
wrote:
>> Did this feature go upstream? So anyone
compiling official
LibreMesh
>> now
>> gets it?
>>
>>
>>
>> SAn:
>>> Hi, I've implemented the failover functionality for babel (package
>>> babeld-auto-gw-mode) and Amuza contributed with testing.
>>>
>>> The pull: request
https://github.com/libremesh/lime-packages/pull/844
>>>
>>> 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].
>>>>>
>>>>
>>>>> Ciao!
>>>>> Ilario
>>>>>
>>>>> [1]:
>>>>> https://github.com/libremesh/lime-packages/issues/93
>>>>> [2]:
>>>>>
>>
https://github.com/libremesh/lime-packages/tree/master/packages/bmx6-auto-g…
>>>>>
>>>>> [3]:
>>>>>
>>
https://github.com/libremesh/lime-packages/tree/master/packages/bmx7-auto-g…
>>>>>
>>>>> [4]:
>>>>>
>>
https://github.com/libremesh/lime-packages/tree/master/packages/batman-adv-…
>>>>>
>>>>> [5]:
>>>>> https://github.com/libremesh/lime-packages/issues/666
>>>>> https://github.com/libremesh/lime-packages/issues/468
>>>>> [6]:
>>>>>
>>
https://github.com/libremesh/lime-packages/tree/master/packages/check-inter…
>>>>>
>>>>> [7]:
>>>>> https://www.irif.fr/~jch/software/babel/babeld.html
>>>>> [8]:
>>>>>
>>
https://openwrt.org/docs/guide-developer/procd-init-scripts#specifying_trig…
>>>>>>
>>>>>>
>>>>> _______________________________________________
>>>>> lime-users mailing list
>>>>> lime-users(a)lists.libremesh.org
>>>>> https://lists.libremesh.org/mailman/listinfo/lime-users
>>>>>
>
>
> _______________________________________________
> lime-users mailing list
> lime-users(a)lists.libremesh.org
> https://lists.libremesh.org/mailman/listinfo/lime-users
>
21 Mar
21 Mar
6:33 p.m.
There you go:
https://github.com/libremesh/lime-web/pull/135
SAn:
Indeed! Do you want to open a pull request? There is a
link in the top right corner.
Thanks!
SAn
On March 20, 2021 6:31:50 PM GMT-03:00, amuza <amuza(a)riseup.net> wrote:
> Shouldn't it be included in the compiling instructions at
> https://libremesh.org/development.html ?
>
>
> amuza:
>> Cool. Thank you for the reminder!
>>
>>
>> SAn:
>>> Hi! Yes :) You have to select the babeld-auto-gw-mode package
>>>
>>> Best!
>>> SAn
>>>
>>> On March 20, 2021 9:03:31 AM GMT-03:00, amuza <amuza(a)riseup.net>
> wrote:
>>>> Did this feature go upstream? So anyone compiling official
> LibreMesh
>>>> now
>>>> gets it?
>>>>
>>>>
>>>>
>>>> SAn:
>>>>> Hi, I've implemented the failover functionality for babel
(package
>>>>> babeld-auto-gw-mode) and Amuza contributed with testing.
>>>>>
>>>>> The pull: request
> https://github.com/libremesh/lime-packages/pull/844
>>>>>
>>>>> 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].
>>>>>>>
>>>>>>
>>>>>>> Ciao!
>>>>>>> Ilario
>>>>>>>
>>>>>>> [1]:
>>>>>>> https://github.com/libremesh/lime-packages/issues/93
>>>>>>> [2]:
>>>>>>>
>>>>
> https://github.com/libremesh/lime-packages/tree/master/packages/bmx6-auto-g…
>>>>>>>
>>>>>>> [3]:
>>>>>>>
>>>>
> https://github.com/libremesh/lime-packages/tree/master/packages/bmx7-auto-g…
>>>>>>>
>>>>>>> [4]:
>>>>>>>
>>>>
>
https://github.com/libremesh/lime-packages/tree/master/packages/batman-adv-…
>>>>>>>
>>>>>>> [5]:
>>>>>>> https://github.com/libremesh/lime-packages/issues/666
>>>>>>> https://github.com/libremesh/lime-packages/issues/468
>>>>>>> [6]:
>>>>>>>
>>>>
> https://github.com/libremesh/lime-packages/tree/master/packages/check-inter…
>>>>>>>
>>>>>>> [7]:
>>>>>>> https://www.irif.fr/~jch/software/babel/babeld.html
>>>>>>> [8]:
>>>>>>>
>>>>
> https://openwrt.org/docs/guide-developer/procd-init-scripts#specifying_trig…
>>>>>>>
>>>>>>>
>>>>>> _______________________________________________
>>>>>> lime-users mailing list
>>>>>> lime-users(a)lists.libremesh.org
>>>>>> https://lists.libremesh.org/mailman/listinfo/lime-users
>>>>>>
>>
>>
>> _______________________________________________
>> lime-users mailing list
>> lime-users(a)lists.libremesh.org
>> https://lists.libremesh.org/mailman/listinfo/lime-users
>>
1137
days inactive
1248
days old
lime-users@lists.libremesh.org
31 comments
5 participants
participants (5)
-
amuza -
Andy Schopf -
guifipedro -
Ilario Gelmetti -
SAn