Gio:
> On Wednesday 26 August 2020 15:14:00 CEST amuza wrote:
>> When preparing my new compilation I added my rules file in the files
>> directory:
>>
>> files/firewall.lime.d/90_my_rules_file.
>
> that way the file end up in `/firewall.lime.d/90_my_rules_file` on the router
> which is not what you want.
>
> If you want your file to stay in
> /etc/firewall.lime.d/90_my_rules_file
> you have to put it in
> files/etc/firewall.lime.d/90_my_rules_file
>
>
Oops, sorry, my mistake... thank you Gio!!
On Aug 26, 2020 15:14, amuza <amuza(a)riseup.net> wrote:
> When preparing my new compilation I added my rules file in the files
> directory:
>
> files/firewall.lime.d/90_my_rules_file.
>
> The new firmware built ok, I installed it in a router and everything
> looked fine, well, almost everything: my rules are not being applied.
The path looks wrong to me, why did you use
files/firewall.lime.d/90_my_rules_file
Instead of
files/etc/firewall.lime.d/90_my_rules_file
?
Ciao,
Ilario
Hi again!
In Lime 17.06 I was adding two basic iptables rules to /etc/firewall.user
Now I have compiled from source (based on OpenWRT 18.06) and see
different firewall files. Where should I add my two lines?
Thank you!
Hi all!
We had a problem on the Element/Matrix chatroom ("Element" is the new
name of Riot chat app): an IRC bridge bot kicked everybody from the channel.
Please re-join the chatroom :)
You can find the direction of the chatroom here:
https://libremesh.org/communication.html
Guifipedro (thanks!!) is checking how to set up a less-problematic IRC
bridge.
Ciao,
Ilario
--
Ilario
iochesonome(a)gmail.com
ilario(a)sindominio.net
Hello,
I have some old routers running LiMe 17.06, they were cooked with my network profile long ago.
Now I have these new bins compiled from source, they are generic.
Can I do an upgrade keeping the configuration? Will it stay?
The default network size used to be /21
Now in lime-example I read /16
Is that the new default size?
Isn't it too large? 65000 hosts communicating in layer-2!
Or maybe the protocols used by Libremesh somehow do some kind of layer-2
routing so that it is not a big collision domain, but many collision
domains into one broadcast domain?
Hi,
As far as I understand the installation now should be done by following
the "Compiling LibreMesh from source code" guide at
https://libremesh.org/development.html
I think that provides firmware without a customized network profile
configuration. Chef did that, but I think there's no chef now. Is there
now any way to avoid manually configuring every router?
Thanks
Hi!!
This is a very interesting question, as we tested just a very small percentage of the available routers.
For sure the router have to be _at least_ supported by OpenWrt, which already do not recommend 4/32 routers [1].
For more discussion on this, please refer to (and contribute to if you can) this discussion: [2].
Ciao!
Ilario
[1] https://openwrt.org/supported_devices/432_warning
[2] https://github.com/libremesh/lime-web/issues/72On Aug 5, 2020 05:44, Pedro Mauro <pmauro(a)posteo.net> wrote:
>
> Hello everyone! I hope you are all well in these times...
>
> I'm planning to deploy a very small network, with maybe three devices.
>
> I have a TL-WR842ND working with LibreMesh and a E2000 with, despite your help, couldn't get to work.
>
> The thing is, I want to get donated routers (or buying used ones) but don't know what features are needed to have a good chance of LibreMesh to work. Also, I can't find any of the routers in the Hardware list here nearby.
>
> I imagine, based on the same list, that two antennas are needed, and also 4/32 flash/ram at least. Is there something else?
>
> Kind regards, Pedro.
>
> --
> Enviado desde mi dispositivo Android con K-9 Mail. Por favor, disculpa mi brevedad.
Hello everyone! I hope you are all well in these times...
I'm planning to deploy a very small network, with maybe three devices.
I have a TL-WR842ND working with LibreMesh and a E2000 with, despite your help, couldn't get to work.
The thing is, I want to get donated routers (or buying used ones) but don't know what features are needed to have a good chance of LibreMesh to work. Also, I can't find any of the routers in the Hardware list here nearby.
I imagine, based on the same list, that two antennas are needed, and also 4/32 flash/ram at least. Is there something else?
Kind regards, Pedro.
--
Enviado desde mi dispositivo Android con K-9 Mail. Por favor, disculpa mi brevedad.
A new big project from the creator of the (nowadays abandoned) Ninux map
server "Nodeshot".
-------- Forwarded Message --------
Subject: [Nodeshot] Goodbye Nodeshot, Hello OpenWISP 2
Date: Thu, 16 Jul 2020 13:12:15 -0500
From: Federico Capoano <federico.capoano(a)gmail.com>
Reply-To: Nodeshot <nodeshot(a)ml.ninux.org>
To: nodeshot(a)ml.ninux.org
Hi everyone,
it took me a long time to recognize this, but the nodeshot
<https://github.com/ninuxorg/nodeshot> project is dead and I think it's
good for me to officially state my departure from it.
It's been an incredible experience and I want to thank everyone who
contributed and used it in the golden years of Ninux (2012-2017) and
other communities.
I moved onto working full time (again, but this time with my own company
funded by my own consulting work) on OpenWISP 2 <http://openwisp.org/>,
which is also built in python and django (the first generation was built
in Ruby and Ruby on Rails).
Over the years I tried to migrate some of the features of nodeshot in
OpenWISP, especially those ones about monitoring the status of the
network as seen by dynamic routing protocols
<https://github.com/openwisp/openwisp-network-topology/>, but I was not
successful in migrating all the features because of lack of resources.
That said, OpenWISP aims to become a framework on which is possible to
build applications like nodeshot on top of it. The project is alive and
steadily growing, there are more users, contributors, companies that use
it and fund its improvement (see the activity feed to verify
<http://openwisp.org/activity.html>), so I encourage anybody that is
still interested in the ideas we were working in nodeshot and want to
contribute to see those come to light to reach us out in the OpenWISP
project <http://openwisp.org/support.html>.
If anybody wants to maintain the code of nodeshot in its current form,
please get in touch with the Ninux organization administrators which can
give you write access to it.
Best regards
Federico Capoano
