-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi everyone ;) I'm writing to the users list of Libre Mesh to announce
that we are starting a mesh network in Oaxaca de Juarez, Mexico.
I met Guido some months ago, and after hearing what has been done with
Alter Mundi in Argentina we decided to base our network on the Libre
Mesh firmware.
We already got 10 TL-WDR3500 to start experimenting. We did some
initial tests with flashing the standard firmware and everything seems
to work es expected :)
We'll try to go with the default network topology and see if it scales
appropriately. Any tips/tricks/insights? What are the canonical next
steps?
Cheers
Ciaby
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJVJBGCAAoJEPU83OtbD4fQUw0P/j/qidZK0xSZ0BnYcgzlAw4F
Lf9/1qySn/ZrqVl9AxCUNMgabQf0wnMR/qyn4m/doDQm+rZFnTj12eSt2RkGb3Ab
bjzBhVzsbkUmrXvaGvqJGJ2SmmaiiKPck/FtZAts0Pr6Z3Lxy9QiGHhnkBg2hkUL
XJIZ25pHm9CEmP9cU5NcDiV2POSIgx0VqEcX4GRje1M2T6LQn9wnjIThKdK8z5yj
d/N5KPfXFllSTbPQilHEbQEydBf1gJPbmR/hcGNE7VV2DgFlLVlCgKZDkqbeNcKP
CP0tOiKHX6UFZNEIHDT7gNu1yQqM/LSmFegem+gfeCUFHUpKTBBga7fIs2pw0DSh
z+DV1Cho4L+OTpL0+QVP9oZ6gkVkUJxaT4TahJOcJGQzITpeq+e2ZgD+tmDgkB06
tJMjeFhNVd+aHTAHss7hIQIr6OOcwx0NLSPvRkpP1bawiqXG9nXXLgEPLTBGf7xu
KFPe3GmWEWvVlzmbxFEmBONpX6fYtg29kccwteuvtSCxdmkte/dME3GkmjyXFJSz
4n9BM5g6Ix99nwwuJX9Ln7E/N+DtGOkdm3FwdcgNZdWqd8TywFgpP5L4tVqAAYqa
oEuMo7bqqRvhkxBNG1xawQstt2QXKEaZCx13aw7m5E0dlP/QVqn5nQMM0mw2aSp6
VY1dmXCCrGnYH2DSBN2m
=IFzl
-----END PGP SIGNATURE-----
Hello there... it's me again :)
I got the image from Gui/DeltaLibre running, I changed the lime-defaults
according to our needs, did the lime-config/uci commit/reboot steps and
everything seems to work fine.
However, I still have some questions:
- How to mark a node as a permanent gateway? Can i set it in
lime-defaults or it's better to just set it in the node-specific lime file?
- Why bmx6 doesn't recognise the other nodes? I basically left the
batman-adv/bmx6 as it was, batman-adv seems to work fine, but bmx6
doesn't recognise the other nodes.
- What's the correct way to assign a IPv6 address space? Does it have to
be public or private? Where do you get your IPv6 blocks assigned?
- Can someone have a look at my config? :)
I'm attaching the current lime-defaults file to this email.
Cheers!
Ciaby
Hi!
Today I was trying to setup a TL-WDR3600 with Libre-Mesh for a specific
setup.
I share here some doubts/strange things:
1)
I still see the "br-lan: received packet on bat0 with own address as
source address" every 10 seconds, even if the router is not connected to
any cable and the wifi is switched off. The problem is known [a] but
marked as not possible to solve [b].
2)
I was expecting the default IPv4 to be autocompleted using MAC address,
something like 192.0.2.%M6 (%M6 = the last field of MAC address) indeed
the standard configuration for IPv4 is
config lime network
option main_ipv4_address '192.0.2.0/24'
resulting in
root@LiMeNode-dd6800:~# ip -4 address show br-lan
6: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP group default
inet 192.0.2.0/24 brd 192.0.2.255 scope global br-lan
valid_lft forever preferred_lft forever
that is a awful ip for an host because it is indeed a subnet identifier
[c] (using %M6 this would happen only if the mac address ends with 00).
3)
A dev (maybe G10?) suggested me to deselect in menuconfig the
Network/odhcpd [d]. Is odhcpd a problem? Anyway I need a dhcp server so
I selected dnsmasq-dhcpv6.
4)
Neither dnsmasq nor dnsmasq-dhcpv6 are a dependency of
dnsmasq-lease-share, why? (anyway up to now I don't need lease-share)
5)
At the WAN port I will connect the ADSL modem, so it seemed a good idea
to specify this in the /etc/config/lime file:
config net eth0_2 #this name can't contain points
list protocols 'wan'
But then I get this:
root@LiMeNode-dd6800:/etc/config# lime-config
Clearing wireless config...
Clearing network config...
Disabling odhcpd
sh: /etc/init.d/odhcpd: not found
Cleaning dnsmasq
Disabling 6relayd...
/usr/lib/lua/lime/network.lua:184: table index is nil
stack traceback:
/usr/bin/lime-config:13: in function </usr/bin/lime-config:13>
[C]: in function 'foreach'
/usr/lib/lua/lime/config.lua:21: in function 'foreach'
/usr/lib/lua/lime/network.lua:184: in function
</usr/lib/lua/lime/network.lua:182>
[C]: in function 'xpcall'
/usr/bin/lime-config:13: in function 'main'
/usr/bin/lime-config:29: in main chunk
[C]: ?
Configuring system...
Let uhttpd listen on IPv4/IPv6
(the error about odhcpd can be safely ignored)
G10 suggested me to add the interface name via linux_name [e]
config net eth0_2
list protocols 'wan'
option linux_name 'eth0.2'
and I realized that in order to work this section needs the package
lime-proto-wan, a warning about the missing package could be useful.
6)
Having removed the OpenWRT's firewall (on LiMe dev's suggestion [f]) the
masquerading from lan to wan wasn't there, so I added
iptables -t nat -A POSTROUTING -o eth0.2 -j MASQUERADE
in /etc/rc.local (thanks to G10 for this indication).
Wouldn't be better to include the masquerading in lime-proto-wan?
Obviously this should also check is the firewall package is present and
in this case avoid running the masquerade command.
Something similar is this already present in bmx6-auto-gw-mode [g].
7)
On a clean LiMe installation, ssuing
uci show 1> /dev/null
I get
uci: Entry not found
Can you also see this? I can't get what is missing...
8)
In a setup where I connect both a Libre-Mesh device and a airos device
to the same port of the WDR3600 (via a switch) [h], do I need to use the
lime-hwd-ground-routing? I think not so because there's only one
non-LiMe device connected.
Thanks!
Ilario
[a] http://lists.libre-mesh.org/pipermail/dev/2014-March/000315.html
[b] http://libre-mesh.org/issues/32
[c] https://en.wikipedia.org/wiki/IPv4#Addresses_ending_in_0_or_255
[d] http://wiki.ninux.org/Libre-Mesh#Selezionare_i_moduli_di_Libre-Mesh
[e]
https://github.com/libre-mesh/lime-packages/blob/develop/packages/lime-syst…
[f]
http://dev.libre-mesh.org/projects/libre-mesh/wiki/Compile_Manually#Startin…
[g]
https://github.com/libre-mesh/lime-packages/blob/0a29a26894ffb73366bc6d6d2b…
[h] http://uz.sns.it/~ilario/ninux-verona-ilario-architecture-201506.png
--
Ilario Gelmetti
iochesonome(a)gmail.com
igelmetti(a)iciq.es
ilario.gelmetti(a)estudiants.urv.cat
On 05/31/2015 07:59 PM, Nemesis wrote:
> Se posso permettermi di dare un consiglio, penso che la
> documentazione in formato ResTructuredText o Markdown conservata in
> un repository github sia la cosa migliore.
Concordo anch'io sull'avere la documentazione in un repo.
Se non è troppo grande può stare tranquillamente nello stesso repo del
codice, così si possono versionare insieme e avere la documentazione di
una release nello stesso commit di quella release.
On Sun, 31 May 2015 20:33:02 +0200
Ilario Gelmetti <iochesonome(a)gmail.com> wrote:
> Sarebbe figo, però ormai abbiamo iniziato a scriverla sui wiki e non
> mi sembra affatto una buona idea spostarla/copiarla.
> Eppoi il sito di libre-mesh ha anche la funzione wiki, mi sembra
> naturale usarla per metterci la documentazione di libre-mesh...
Il sito di libre-mesh è una istanza di Redmine e il wiki è una
funzionalità davvero marginale di quel programma...
le categorie non ci sono: si possono solo fare relazioni padre-figlio
tra le pagine (e si fa con il tasto "rename"), e le categorie sono
fondamentali nella documentazione per distinguere le pagine importanti
tipo "routing in libre-mesh" da pagine molto specifiche o di reference
("how-to: compilare libre-mesh su PPC").
Se vuoi portarti la documentazione off-line banalmente non puoi, a meno
che non salvi tutte le pagine una per una perché non esiste nessun tool
decente (e spero che qualcuno smentisca) per esportare il wiki
intero o una categoria... quindi una volta che scrivi nel wiki di
redmine non puoi migrare facilmente a niente di diverso, neanche un
altro sito che usa redmine.
Insomma, è per dire che il wiki di redmine non è un wiki normale, è una
roba che serve solo per sopperire a esigenze di sviluppo o per dare
link a risorse che non fanno parte della documentazione vera; per fare
un esempio un progetto grosso che usa redmine dall'inizio alla fine è
gnuradio [1], loro hanno nel wiki un po' di link a vari tutorial, dati
d'esempio e pagine organizzative, ma il manuale vero è fatto con Doxygen
e Sphinx (perché in realtà il bello di GNURadio sono le sue API).
Capisco che avere un wiki permetta a più persone di scrivere qualcosa
perché viene meno la sensazione di responsabilità che si avrebbe
committando su un repo e perché è effettivamente più facile da usare,
però che sia un wiki vero almeno, tipo dokuwiki o mediawiki :)
Metto in CC lime-users perché credo che a questo punto, con diverse
reti che vogliono iniziare _effettivamente_ ad usarlo converrebbe avere
delle linee guida per la documentazione decise insieme agli
sviluppatori.
[1] http://gnuradio.org/redmine/projects/gnuradio/wiki
Hi all,
when we first tried to install libre-mesh (on a ubnt bullet and a
picostation, but that's not the point) we were confused by the fact
that the usual
ping6 ff02::1%eth0
that we do in order to discover the addresses of the available devices
in the net was NOT working as expected, it was like each device was
isolated from the rest of the net.
We identified the problem with the multicast mode of batman-adv, in
fact with
batctl multicast_mode 0
everything works fine again.
Can anyone reproduce this behavior?
According to
http://www.open-mesh.org/projects/batman-adv/wiki/Multicast-optimizations
it seems that batman drops the data when there are no listeners.
A multicast ping6 actually doesn't have registered listeners, so it
seems an exception to the rule, shall we file a bug in batman-adv or
are we missing something?
On Wednesday, April 29, 2015 09:57:40 AM Ilario Gelmetti wrote:
> L'unica "perdita di tempo" avviene su ethernet dove praticamente non
> c'è contesa per il canale e fa usare un po' più processore alle
> antenne, in ogni caso il throughput ne risente solo quando ci
> avviciniamo ai 100Mbit di traffico esplicitamente tra le due antenne.
>
> Se c'è un collo di bottiglia potrebbe essere la cpu delle antenne che
> devono tagliare e ricomporre... boh, bisogna provare. In generale
> volevo solo dire che il problema è molto isolato e quindi potrebbe non
> essere un problema
Io credo che il collo di bottiglia sia proprio il cervello dell'antenna, tieni
in conto che la CPU e' un ARM 400MHz ora non so a quanto va il bus che collega
la porta ethernet alla CPU ma di solito e' piu' lento della CPU, e quanti
cicli ci CPU servono per tirar su dalla ethernet un pacchetto e farglielo
processare a batman, la frammentazione da sola moltiplicherebbe almeno x2
tutto il lavoro, per cui potrebbe proprio dargli il colpo di grazia alle
performance.
Per esperienza quando succedono robe inspiegabili alla fine e' sempre colpa
dell' mtu :p e comunque io cercherei di ridurre le variabili in gioco il piu'
possibile ;)
P.S. sta roba starebbe bene mettere in CC la lista lime-users su cui si parla
anche italiano
Bella!
tnx for the link.
we digested it already.
As far as it looks now
there are some basic questions we try to to get the answer looking at
the source.
Besides this is alot of tendoius work, the general situation about
documentations makes us feel "to be left alone in the dark"
We do know for some reason documentation in opensource is mostly
missing or crytic hidden in the source, there is a very nice
counter-example in various versions of freifunk germany.
As it seems we have to make a decision wether to go with lime and do
all the documentaion by ourselfs or rather to implement a freifunk
version for our needs.
As soon we have finished som overview for lime documentation we will
publish the link.
Is there any preference towards the way/system to build/publish a
documentation ?
regards
3zl
2015-01-27 14:00 GMT+02:00 <users-request(a)lists.libre-mesh.org>:
> Send users mailing list submissions to
> users(a)lists.libre-mesh.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.libre-mesh.org/mailman/listinfo/users
> or, via email, send a message with subject or body 'help' to
> users-request(a)lists.libre-mesh.org
>
> You can reach the person managing the list at
> users-owner(a)lists.libre-mesh.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of users digest..."
>
>
> Asuntos del día:
>
> 1. Re: starting with LiMe (Gioacchino Mazzurco)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 27 Jan 2015 12:28:57 +0100
> From: Gioacchino Mazzurco <gio(a)eigenlab.org>
> To: 3zl Trizonelabs <trizonelabs(a)gmail.com>
> Cc: users <users(a)lists.libre-mesh.org>
> Subject: Re: [lime-users] starting with LiMe
> Message-ID: <11138175.r60rYvaLpJ@giomium>
> Content-Type: text/plain; charset="us-ascii"
>
> Please keep users(a)lists.libre-mesh.org in CC
>
>
> On Friday, January 23, 2015 05:30:02 PM 3zl Trizonelabs wrote:
>> Naturally we do struggle with the lime configuration, as we could not
>> find any valuable informations.
>> To get some locals to work with the system we have to prepare a
>> conciese howto for build, deploy & operate the nodes in hard- and
>> software.
>
> In the source there is some documentation about options
>
> https://github.com/libre-mesh/lime-packages/blob/develop/packages/lime-syst…
>
>
>> At the moment we spend some hours sifting though the source with
>> OpenGrok ( http://en.wikipedia.org/wiki/OpenGrok ) and prepare a
>> documentation structure with MindjetManager and export the HTML to a
>> website where you could follow the outcome of our documentation
>> effords
>
> Can you share the URL ?
>
>
> ------------------------------
>
> _______________________________________________
> users mailing list
> users(a)lists.libre-mesh.org
> https://lists.libre-mesh.org/mailman/listinfo/users
>
>
> Fin de Resumen de users, Vol 3, Envío 4
> ***************************************
Please keep users(a)lists.libre-mesh.org in CC
On Friday, January 23, 2015 05:30:02 PM 3zl Trizonelabs wrote:
> Naturally we do struggle with the lime configuration, as we could not
> find any valuable informations.
> To get some locals to work with the system we have to prepare a
> conciese howto for build, deploy & operate the nodes in hard- and
> software.
In the source there is some documentation about options
https://github.com/libre-mesh/lime-packages/blob/develop/packages/lime-syst…
> At the moment we spend some hours sifting though the source with
> OpenGrok ( http://en.wikipedia.org/wiki/OpenGrok ) and prepare a
> documentation structure with MindjetManager and export the HTML to a
> website where you could follow the outcome of our documentation
> effords
Can you share the URL ?
Hello @all,
we are trying to build a community in greece in the area of Korinth gulf
With this we have to decide which system to use.
As we do have experience with batman-adv on about 20 nodes, we are
analysing libre-mesh system and gather as much informations &
documentation as possible.
We also had a deeper look at some Freifunk systems.
At this moment we do lack setup & technical documentation of the
libre-mesh and asking for advice where to find.
thank you for your cooperation
3zl(Reinhard)
