20 May
2014
20 May
'14
10:33 p.m.
Hi,
I have compiled the firmware using lime-build for tl-mr3020, and then
installed the firmware on two routers. The mesh works, they can see
each other and I can connect to them as Access Points. Now I have two
questions:
1. How do I connect a router to the Internet?
2. How do I share this connection with the mesh?
For (1), I tried scanning for wifi networks but I got an error that
libiwinfo-lua was missing. I connected to a network through ssh using
wpa_supplicant and installed libiwinfo-lua, so now I can properly
connect from the web interface. It seems libiwinfo-lua should be
installed by default, shouldn't it?
For (2), I'm not quite sure how to proceed.
Ramiro
21 May
21 May
12:16 a.m.
----- Mensaje original -----
De: "Ramiro Polla"
<ramiro.polla(a)gmail.com>
Para: dev(a)lists.libre-mesh.org
Enviados: Miércoles, 21 de Mayo 2014 0:33:14
Asunto: [lime-dev] I have installed the firmware. Now what? =)
Hi,
I have compiled the firmware using lime-build for tl-mr3020, and then
installed the firmware on two routers. The mesh works, they can see
each other and I can connect to them as Access Points. Now I have two
questions:
1. How do I connect a router to the Internet?
2. How do I share this connection with the mesh?
For (1), I tried scanning for wifi networks but I got an error that
libiwinfo-lua was missing. I connected to a network through ssh using
wpa_supplicant and installed libiwinfo-lua, so now I can properly
connect from the web interface. It seems libiwinfo-lua should be
installed by default, shouldn't it?
For (2), I'm not quite sure how to proceed.
Ramiro
Hello, Ramiro, wellcome to Libre-mesh.
Normally we connect router to internet (or to other network) through ethernet. Libre-mesh
works in that way to default and share this connection by default. Can not do it in that
way? I understand that you are trying to use WiFi interface to mesh + AP + client. Is it?
I think you can success, but is strange for me.
About libiwinfo-lua I don't know if is necessary by default. We make scan with
"iw mesh0 scan", but we don't need it normally, and we don't want to
offer options that are going to complicate understanding of Libre-mesh (we are going to
delete options). We don't design Libre-mesh to act as a client, of course you can do
it. And we like to hear your needs. Why don't use ethernet?
2:29 a.m.
Hi al,
2014-05-20 21:16 GMT-03:00 al <al(a)blogmail.cc>cc>:
We have a project in Brazil to use Mesh Networks in demonstrations and
protests to provide a Wireless LAN and Internet to the crowds. There
are people in the crowd with routers using mesh networks extending the
reach of regular Internet connections that people open up at home. The
LAN can be used for quick and free communication that does not depend
on 3G or another solution. The routers that are close to Internet
connections are always seeking for new connections. Due to the fact
that the crowd is always walking, we can't connect the nodes to
ethernet.
Currently we use OpenWRT+OLSR and a complicated configuration, I'd
like to replace that with a better and easier to use solution. I have
no problem using the command line to connect, but we want more people
to adopt this, and that way they'd need to do it with a simpler
interface. That's why I thought about using libre-mesh as a base
system.
So ethernet is shared by default, but how would I configure another
source for sharing? (a 3g/4g modem, another wireless adapter, or even
the same wifi acting as mesh+AP)
Ramiro
De:
"Ramiro Polla" <ramiro.polla(a)gmail.com>
Para: dev(a)lists.libre-mesh.org
Enviados: Miércoles, 21 de Mayo 2014 0:33:14
Asunto: [lime-dev] I have installed the firmware. Now what? =)
I have compiled the firmware using lime-build for tl-mr3020, and then
installed the firmware on two routers. The mesh works, they can see
each other and I can connect to them as Access Points. Now I have two
questions:
1. How do I connect a router to the Internet?
2. How do I share this connection with the mesh?
For (1), I tried scanning for wifi networks but I got an error that
libiwinfo-lua was missing. I connected to a network through ssh using
wpa_supplicant and installed libiwinfo-lua, so now I can properly
connect from the web interface. It seems libiwinfo-lua should be
installed by default, shouldn't it?
For (2), I'm not quite sure how to proceed.
Ramiro
Hello, Ramiro, wellcome to Libre-mesh.
Normally we connect router to internet (or to other network) through ethernet. Libre-mesh
works in that way to default and share this connection by default. Can not do it in that
way? I understand that you are trying to use WiFi interface to mesh + AP + client. Is it?
I think you can success, but is strange for me.
About libiwinfo-lua I don't know if is necessary by default. We make scan with
"iw mesh0 scan", but we don't need it normally, and we don't want to
offer options that are going to complicate understanding of Libre-mesh (we are going to
delete options). We don't design Libre-mesh to act as a client, of course you can do
it. And we like to hear your needs. Why don't use ethernet? 
9:17 a.m.
On Tuesday 20 May 2014 23:29:21 Ramiro Polla wrote:
Currently we use OpenWRT+OLSR and a complicated
configuration, I'd
like to replace that with a better and easier to use solution. I have
no problem using the command line to connect, but we want more people
to adopt this, and that way they'd need to do it with a simpler
interface. That's why I thought about using libre-mesh as a base
system.
Yeah you can use this as base system you simply need to develop a lime module
that does that for you, start finding a little but meningful name something
like lime-* (look at other lime module name for inspiration)
And if you can do it by your self with shell of course you will be able to
develop a lime module in lua, that integrate with lime ecosistem
So ethernet is shared by default, but how would I
configure another
source for sharing?
What you mean by sharing ethernet? If you mean sharing an internet connection
available trought ethernet it is in plan but not implemented yet
(a 3g/4g modem,
Yet another module you can implement (I have no time for this now)
another wireless adapter
Yet another module you can implement (I have no time for this now)
or even
the same wifi acting as mesh+AP)
I doubt this is doable, but it it is, or if i am misunderstanding here it goes
the mantra
Yet another module you can implement (I have no time for this now)
;)
4:43 p.m.
Hi,
2014-05-21 6:17 GMT-03:00 Gioacchino Mazzurco <gmazzurco89(a)gmail.com>om>:
Mesh+AP+Client works as long as they're on the same channel. (it works
currently with our OLSR setup).
On Tuesday 20 May 2014 23:29:21 Ramiro Polla wrote:
Hm, I'm confused now. Al says it's supported but you're saying it
isn't. (I haven't tested yet)
Currently we use OpenWRT+OLSR and a complicated
configuration, I'd
like to replace that with a better and easier to use solution. I have
no problem using the command line to connect, but we want more people
to adopt this, and that way they'd need to do it with a simpler
interface. That's why I thought about using libre-mesh as a base
system.
Yeah you can use this as base system you simply need to develop a lime module
that does that for you, start finding a little but meningful name something
like lime-* (look at other lime module name for inspiration)
And if you can do it by your self with shell of course you will be able to
develop a lime module in lua, that integrate with lime ecosistem
So ethernet is shared by default, but how would I
configure another
source for sharing?
What you mean by sharing ethernet? If you mean sharing an internet connection
available trought ethernet it is in plan but not implemented yet (a 3g/4g
modem,
Yet another module you can implement (I have no time for this now)
another wireless adapter
Yet another module you can implement (I have no time for this now)
or even
the same wifi acting as mesh+AP)
I doubt this is doable, but it it is, or if i am misunderstanding here it goes
the mantra Yet another module you can implement (I have no time
for this now)
;)
I understand I can add modules to implement things. That is not the
issue. See below.
[...]
this is still not implemented yet, so at moment you
need to configure manually
a node to connect to the internet and annource the default route with bmx6
So it seems that after I get a successful connection, I have to
announce the default route with bmx6. This is probably what I am
looking for. Where can I get more information related to this and
libre-mesh's current setup?
Ramiro
22 May
22 May
6:36 a.m.
----- Mensaje original -----
Mesh+AP+Client works as long as they're on the same channel. (it
works
currently with our OLSR setup).
Great, so have no problem to work with MX6+BATMAN-adv setup :)
Ok, so if you can get a successful connection for yourself, you can announce the default
route with bmx6. There's some ways, but I think is better that Gioacchino or anybody
with more technical experience than me, say best way.
That's my /etc/config/lime (i.e. you can change "option primary_dev"):
----
config lime 'network'
option primary_dev 'eth0'
list vlans '10'
list protos 'bmx6'
list protos 'batadv'
option ipv4_net '192.168.11.0/24'
option ipv6_net '2a00:1508:1:f820::/64'
config lime 'wireless'
option ssid 'garraflliure.guifi.net'
option mesh_bssid 'ca:fe:00:c0:ff:ee'
option mesh_mcast_rate_2ghz '24000'
option mesh_mcast_rate_5ghz '6000'
list mesh_channel_2ghz '11'
list mesh_channel_2ghz '1'
list mesh_channel_5ghz '36+'
----
In uci you have:
lime.network.primary_dev
(and other lime.network.*)
When you success manually, we can take a look to think the module :)
[1] http://ca.wiki.guifi.net/wiki/Unsolclic (sorry catalan only, summary: list of commands
(more or less "automatic generated") to configure a device just copying &
pasting in shell, in this case (based on OpenWrt) is a list of uci commands).
De: "Ramiro Polla"
<ramiro.polla(a)gmail.com>
Para: "libre-mesh developement" <dev(a)lists.libre-mesh.org>
Enviados: Miércoles, 21 de Mayo 2014 18:43:04
Asunto: Re: [lime-dev] I have installed the firmware. Now what? =)
Hi,
2014-05-21 6:17 GMT-03:00 Gioacchino Mazzurco
<gmazzurco89(a)gmail.com>om>:
Gioacchino is right. I have supported it in Libre-mesh, but with justoneclick (guifi.net
style[1]), not just by default. Sorry. But this is planned to be supported by default.
On Tuesday 20 May 2014 23:29:21 Ramiro Polla
wrote:
Hm, I'm confused now. Al says it's supported but you're saying it
isn't. (I haven't tested yet) Currently we use OpenWRT+OLSR and a complicated
configuration, I'd
like to replace that with a better and easier to use solution. I
have
no problem using the command line to connect, but we want more
people
to adopt this, and that way they'd need to do it with a simpler
interface. That's why I thought about using libre-mesh as a base
system.
Yeah you can use this as base system you simply need to develop a
lime module
that does that for you, start finding a little but meningful name
something
like lime-* (look at other lime module name for inspiration)
And if you can do it by your self with shell of course you will be
able to
develop a lime module in lua, that integrate with lime ecosistem
So ethernet is shared by default, but how would I
configure
another
source for sharing?
What you mean by sharing ethernet? If you mean sharing an internet
connection
available trought ethernet it is in plan but not implemented yet (a 3g/4g
modem,
Yet another module you can implement (I have no time for this now)
another wireless adapter
Yet another module you can implement (I have no time for this now)
or even
the same wifi acting as mesh+AP)
I doubt this is doable, but it it is, or if i am misunderstanding
here it goes
the mantra Yet another module you can implement (I have no
time for this now)
;)
I understand I can add modules to implement things. That is not the
issue. See below.
[...]
this is still not implemented yet, so at moment
you need to
configure manually
a node to connect to the internet and annource the default route
with bmx6
So it seems that after I get a successful connection, I have to
announce the default route with bmx6. This is probably what I am
looking for. Where can I get more information related to this and
libre-mesh's current setup?
6:47 a.m.
----- Mensaje original -----
De: "al" <al(a)blogmail.cc>
Para: "libre-mesh developement" <dev(a)lists.libre-mesh.org>
Enviados: Jueves, 22 de Mayo 2014 8:36:44
Asunto: Re: [lime-dev] I have installed the firmware. Now what? =)
----- Mensaje original -----
Mesh+AP+Client works as long as they're on the same channel. (it
works
currently with our OLSR setup).
Great, so have no problem to work with MX6+BATMAN-adv setup :)
Ok, so if you can get a successful connection for yourself, you can
announce the default route with bmx6. There's some ways, but I think
is better that Gioacchino or anybody with more technical experience
than me, say best way.
That's my /etc/config/lime (i.e. you can change "option
primary_dev"):
----
config lime 'network'
option primary_dev 'eth0'
list vlans '10'
list protos 'bmx6'
list protos 'batadv'
option ipv4_net '192.168.11.0/24'
option ipv6_net '2a00:1508:1:f820::/64'
config lime 'wireless'
option ssid 'garraflliure.guifi.net'
option mesh_bssid 'ca:fe:00:c0:ff:ee'
option mesh_mcast_rate_2ghz '24000'
option mesh_mcast_rate_5ghz '6000'
list mesh_channel_2ghz '11'
list mesh_channel_2ghz '1'
list mesh_channel_5ghz '36+'
----
In uci you have:
lime.network.primary_dev
(and other lime.network.*)
Hey, sorry, also take a look in uci to
bmx6.lm_eth_bmx6=dev
bmx6.lm_eth_bmx6.dev=...
network.wan=interface
network.wan.ifname=...
But wait another answer for a best way :)
De: "Ramiro Polla"
<ramiro.polla(a)gmail.com>
Para: "libre-mesh developement" <dev(a)lists.libre-mesh.org>
Enviados: Miércoles, 21 de Mayo 2014 18:43:04
Asunto: Re: [lime-dev] I have installed the firmware. Now what? =)
Hi,
2014-05-21 6:17 GMT-03:00 Gioacchino Mazzurco
<gmazzurco89(a)gmail.com>om>:
Gioacchino is right. I have supported it in Libre-mesh, but with
justoneclick (guifi.net style[1]), not just by default. Sorry. But
this is planned to be supported by default.
On Tuesday 20 May 2014 23:29:21 Ramiro Polla
wrote:
Hm, I'm confused now. Al says it's supported but you're saying it
isn't. (I haven't tested yet) Currently we use OpenWRT+OLSR and a complicated
configuration,
I'd
like to replace that with a better and easier to use solution. I
have
no problem using the command line to connect, but we want more
people
to adopt this, and that way they'd need to do it with a simpler
interface. That's why I thought about using libre-mesh as a base
system.
Yeah you can use this as base system you simply need to develop a
lime module
that does that for you, start finding a little but meningful name
something
like lime-* (look at other lime module name for inspiration)
And if you can do it by your self with shell of course you will
be
able to
develop a lime module in lua, that integrate with lime ecosistem
So ethernet is shared by default, but how would I
configure
another
source for sharing?
What you mean by sharing ethernet? If you mean sharing an
internet
connection
available trought ethernet it is in plan but not implemented yet (a 3g/4g
modem,
Yet another module you can implement (I have no time for this
now)
another wireless adapter
Yet another module you can implement (I have no time for this
now)
or even
the same wifi acting as mesh+AP)
I doubt this is doable, but it it is, or if i am misunderstanding
here it goes
the mantra Yet another module you can implement (I have no
time for this
now)
;)
I understand I can add modules to implement things. That is not the
issue. See below.
[...]
this is still not implemented yet, so at moment
you need to
configure manually
a node to connect to the internet and annource the default route
with bmx6
So it seems that after I get a successful connection, I have to
announce the default route with bmx6. This is probably what I am
looking for. Where can I get more information related to this and
libre-mesh's current setup?
When you success manually, we can take a look to think the module :)
[1] http://ca.wiki.guifi.net/wiki/Unsolclic (sorry catalan only,
summary: list of commands (more or less "automatic generated") to
configure a device just copying & pasting in shell, in this case
(based on OpenWrt) is a list of uci commands).
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
8:26 a.m.
Hi.
I've been reading this thread in diagonal, so sorry if I repeat
something which has been said. My points are:
1. libiwinfo-lua must be included, we removed the full luci dependency
some weeks ago to enable only the specific packets, this library was
missing. Thanks!
2. take into account that libre-mesh is in development, which means
there are many features not yet implemented. As you noticed, the
automatic Internet sharing is one.
3. if you want to deploy a production network consider using other
temporal solutions such as http://qmp.cat which will be compatible with
libre-mesh. However, seems that you have quite good technical skills, so
having your contributions in libre-mesh would be very useful.
4. it is completely possible to use a single wifi device as adhoc+AP
5. to share Internet connection check the bxm6 documentation (bmx6 -c
tunOut inet /n 0.0.0.0/0 && uci commit)
On 22/05/14 08:47, al wrote:
----- Mensaje original -----
--
./p4u
De: "al" <al(a)blogmail.cc>
Para: "libre-mesh developement" <dev(a)lists.libre-mesh.org>
Enviados: Jueves, 22 de Mayo 2014 8:36:44
Asunto: Re: [lime-dev] I have installed the firmware. Now what? =)
----- Mensaje original -----
Great, so have no problem to work with MX6+BATMAN-adv setup :)
Ok, so if you can get a successful connection for yourself, you can
announce the default route with bmx6. There's some ways, but I think
is better that Gioacchino or anybody with more technical experience
than me, say best way.
That's my /etc/config/lime (i.e. you can change "option
primary_dev"):
----
config lime 'network'
option primary_dev 'eth0'
list vlans '10'
list protos 'bmx6'
list protos 'batadv'
option ipv4_net '192.168.11.0/24'
option ipv6_net '2a00:1508:1:f820::/64'
config lime 'wireless'
option ssid 'garraflliure.guifi.net'
option mesh_bssid 'ca:fe:00:c0:ff:ee'
option mesh_mcast_rate_2ghz '24000'
option mesh_mcast_rate_5ghz '6000'
list mesh_channel_2ghz '11'
list mesh_channel_2ghz '1'
list mesh_channel_5ghz '36+'
----
In uci you have:
lime.network.primary_dev
(and other lime.network.*)
Hey, sorry, also take a look in uci to
bmx6.lm_eth_bmx6=dev
bmx6.lm_eth_bmx6.dev=...
network.wan=interface
network.wan.ifname=...
But wait another answer for a best way :)
De: "Ramiro Polla"
<ramiro.polla(a)gmail.com>
Para: "libre-mesh developement" <dev(a)lists.libre-mesh.org>
Enviados: Miércoles, 21 de Mayo 2014 18:43:04
Asunto: Re: [lime-dev] I have installed the firmware. Now what? =)
Hi,
2014-05-21 6:17 GMT-03:00 Gioacchino Mazzurco
<gmazzurco89(a)gmail.com>om>:
Gioacchino is right. I have supported it in Libre-mesh, but with
justoneclick (guifi.net style[1]), not just by default. Sorry. But
this is planned to be supported by default.
On Tuesday 20 May 2014 23:29:21 Ramiro Polla
wrote:
> Currently we use OpenWRT+OLSR and a complicated configuration,
> I'd
> like to replace that with a better and easier to use solution. I
> have
> no problem using the command line to connect, but we want more
> people
> to adopt this, and that way they'd need to do it with a simpler
> interface. That's why I thought about using libre-mesh as a base
> system.
Yeah you can use this as base system you simply need to develop a
lime module
that does that for you, start finding a little but meningful name
something
like lime-* (look at other lime module name for inspiration)
And if you can do it by your self with shell of course you will
be
able to
develop a lime module in lua, that integrate with lime ecosistem
> So ethernet is shared by default, but how would I configure
> another
> source for sharing?
What you mean by sharing ethernet? If you mean sharing an
internet
connection
available trought ethernet it is in plan but not implemented yet
Hm, I'm confused now. Al says it's supported but you're saying it
isn't. (I haven't tested yet) > (a 3g/4g modem,
Yet another module you can implement (I have no time for this
now)
> another wireless adapter
Yet another module you can implement (I have no time for this
now)
> or even
> the same wifi acting as mesh+AP)
I doubt this is doable, but it it is, or if i am misunderstanding
here it goes
the mantra
Mesh+AP+Client works as long as they're on the same channel. (it
works
currently with our OLSR setup). Yet another module you can implement (I have no
time for this
now)
;)
I understand I can add modules to implement things. That is not the
issue. See below.
[...]
this is still not implemented yet, so at moment
you need to
configure manually
a node to connect to the internet and annource the default route
with bmx6
So it seems that after I get a successful connection, I have to
announce the default route with bmx6. This is probably what I am
looking for. Where can I get more information related to this and
libre-mesh's current setup?
When you success manually, we can take a look to think the module :)
[1] http://ca.wiki.guifi.net/wiki/Unsolclic (sorry catalan only,
summary: list of commands (more or less "automatic generated") to
configure a device just copying & pasting in shell, in this case
(based on OpenWrt) is a list of uci commands).
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
9:27 a.m.
----- Mensaje original -----
De: "Pau" <pau(a)dabax.net>
Para: dev(a)lists.libre-mesh.org
Enviados: Jueves, 22 de Mayo 2014 10:26:05
Asunto: Re: [lime-dev] I have installed the firmware. Now what? =)
Hi.
I've been reading this thread in diagonal, so sorry if I repeat
something which has been said. My points are:
1. libiwinfo-lua must be included, we removed the full luci
dependency
some weeks ago to enable only the specific packets, this library was
missing. Thanks!
Nothing to say.
2. take into account that libre-mesh is in development, which means
there are many features not yet implemented. As you noticed, the
automatic Internet sharing is one.
Nothing to add.
3. if you want to deploy a production network consider using other
temporal solutions such as http://qmp.cat which will be compatible
with
libre-mesh. However, seems that you have quite good technical skills,
so
having your contributions in libre-mesh would be very useful.
For me Libre-mesh is fully working. That's it in our 11 nodes in Jardí Botànic.
It's best way when you need connection in outdoor. That's he needs.
You say that qmp.cat which will be compatible with Libre-mesh. What's the plan of
compatibility?
4. it is completely possible to use a single wifi device as adhoc+AP
Of course, he said to use the little MR3020 as adhoc+AP+client. And he said that success.
Great!
5. to share Internet connection check the bxm6 documentation (bmx6 -c
tunOut inet /n 0.0.0.0/0 && uci commit)
Nothing to add.
On 22/05/14 08:47, al wrote:
----- Mensaje original -----
--
./p4u
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
De: "al" <al(a)blogmail.cc>
Para: "libre-mesh developement" <dev(a)lists.libre-mesh.org>
Enviados: Jueves, 22 de Mayo 2014 8:36:44
Asunto: Re: [lime-dev] I have installed the firmware. Now what? =)
----- Mensaje original -----
Hey, sorry, also take a look in uci to
bmx6.lm_eth_bmx6=dev
bmx6.lm_eth_bmx6.dev=...
network.wan=interface
network.wan.ifname=...
But wait another answer for a best way :)
De: "Ramiro Polla"
<ramiro.polla(a)gmail.com>
Para: "libre-mesh developement" <dev(a)lists.libre-mesh.org>
Enviados: Miércoles, 21 de Mayo 2014 18:43:04
Asunto: Re: [lime-dev] I have installed the firmware. Now what?
=)
Hi,
2014-05-21 6:17 GMT-03:00 Gioacchino Mazzurco
<gmazzurco89(a)gmail.com>om>:
> On Tuesday 20 May 2014 23:29:21 Ramiro Polla wrote:
>> Currently we use OpenWRT+OLSR and a complicated configuration,
>> I'd
>> like to replace that with a better and easier to use solution.
>> I
>> have
>> no problem using the command line to connect, but we want more
>> people
>> to adopt this, and that way they'd need to do it with a simpler
>> interface. That's why I thought about using libre-mesh as a
>> base
>> system.
>
> Yeah you can use this as base system you simply need to develop
> a
> lime module
> that does that for you, start finding a little but meningful
> name
> something
> like lime-* (look at other lime module name for inspiration)
>
> And if you can do it by your self with shell of course you will
> be
> able to
> develop a lime module in lua, that integrate with lime ecosistem
>
>
>> So ethernet is shared by default, but how would I configure
>> another
>> source for sharing?
>
> What you mean by sharing ethernet? If you mean sharing an
> internet
> connection
> available trought ethernet it is in plan but not implemented yet
Hm, I'm confused now. Al says it's supported but you're saying it
isn't. (I haven't tested yet)
Gioacchino is right. I have supported it in Libre-mesh, but with
justoneclick (guifi.net style[1]), not just by default. Sorry. But
this is planned to be supported by default.
>> (a 3g/4g modem,
>
> Yet another module you can implement (I have no time for this
> now)
>
>
>> another wireless adapter
>
> Yet another module you can implement (I have no time for this
> now)
>
>
>> or even
>> the same wifi acting as mesh+AP)
>
> I doubt this is doable, but it it is, or if i am
> misunderstanding
> here it goes
> the mantra
Mesh+AP+Client works as long as they're on the same channel. (it
works
currently with our OLSR setup).
Great, so have no problem to work with MX6+BATMAN-adv setup :)
> Yet another module you can implement (I have no time for this
> now)
> ;)
I understand I can add modules to implement things. That is not
the
issue. See below.
[...]
> this is still not implemented yet, so at moment you need to
> configure manually
> a node to connect to the internet and annource the default route
> with bmx6
So it seems that after I get a successful connection, I have to
announce the default route with bmx6. This is probably what I am
looking for. Where can I get more information related to this and
libre-mesh's current setup?
Ok, so if you can get a successful connection for yourself, you
can
announce the default route with bmx6. There's some ways, but I
think
is better that Gioacchino or anybody with more technical
experience
than me, say best way.
That's my /etc/config/lime (i.e. you can change "option
primary_dev"):
----
config lime 'network'
option primary_dev 'eth0'
list vlans '10'
list protos 'bmx6'
list protos 'batadv'
option ipv4_net '192.168.11.0/24'
option ipv6_net '2a00:1508:1:f820::/64'
config lime 'wireless'
option ssid 'garraflliure.guifi.net'
option mesh_bssid 'ca:fe:00:c0:ff:ee'
option mesh_mcast_rate_2ghz '24000'
option mesh_mcast_rate_5ghz '6000'
list mesh_channel_2ghz '11'
list mesh_channel_2ghz '1'
list mesh_channel_5ghz '36+'
----
In uci you have:
lime.network.primary_dev
(and other lime.network.*)
When you success manually, we can take a look to think the module
:)
[1] http://ca.wiki.guifi.net/wiki/Unsolclic (sorry catalan only,
summary: list of commands (more or less "automatic generated") to
configure a device just copying & pasting in shell, in this case
(based on OpenWrt) is a list of uci commands).
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
9:48 a.m.
Hey al, maybe better than "Nothing to add" is just to add nothing :P
The compatibility between qmp and libremesh is based on:
1. Using the same VLAN tag for the bmx6 network
2. Use the same routing protocol which is bmx6
So once the two networks see each other, they will exchange routes and
you will be able to reach all nodes.
About "libremesh is fully working", I'm not saying the opposite. But you
need to set up several things manually (what you actually do with this
"just-one-click" might be also done from a raw OpenWRT and adding
instructions to install all needed packets), which is not what I
understand for a production firmware for building mesh networks.
The mesh network you manage is quite different that a citizens community
mesh network. You are installing and administration all nodes, however
in a citizen mesh network the users must install them and manage them.
To this end, if you want to allow non technical users to do so, you
should provide a set of tools to do it in a easy way. The internet
sharing is an example, but there is also a big need in automatizing
things and the web interface (user does not want and does not know how
to access throw ssh to the node and execute manual commands).
IMO, libre-mesh will be amazing because the basis architecture is just
amazing. However there is still a lot of work to do to have a production
ready firmware (for qMp we have been developing for almost 4 years and
now we are starting to have a stable-finished version).
Cheers.
On 22/05/14 11:27, al wrote:
----- Mensaje original -----
--
./p4u
De: "Pau" <pau(a)dabax.net>
Para: dev(a)lists.libre-mesh.org
Enviados: Jueves, 22 de Mayo 2014 10:26:05
Asunto: Re: [lime-dev] I have installed the firmware. Now what? =)
Hi.
I've been reading this thread in diagonal, so sorry if I repeat
something which has been said. My points are:
1. libiwinfo-lua must be included, we removed the full luci
dependency
some weeks ago to enable only the specific packets, this library was
missing. Thanks!
Nothing to say.
2. take into account that libre-mesh is in development, which means
there are many features not yet implemented. As you noticed, the
automatic Internet sharing is one.
Nothing to add.
3. if you want to deploy a production network consider using other
temporal solutions such as http://qmp.cat which will be compatible
with
libre-mesh. However, seems that you have quite good technical skills,
so
having your contributions in libre-mesh would be very useful.
For me Libre-mesh is fully working. That's it in our 11 nodes in Jardí Botànic.
It's best way when you need connection in outdoor. That's he needs.
You say that qmp.cat which will be compatible with Libre-mesh. What's the plan of
compatibility?
4. it is completely possible to use a single wifi device as adhoc+AP
Of course, he said to use the little MR3020 as adhoc+AP+client. And he said that success.
Great!
5. to share Internet connection check the bxm6 documentation (bmx6 -c
tunOut inet /n 0.0.0.0/0 && uci commit)
Nothing to add.
On 22/05/14 08:47, al wrote:
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
----- Mensaje original -----
--
./p4u
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
De: "al" <al(a)blogmail.cc>
Para: "libre-mesh developement" <dev(a)lists.libre-mesh.org>
Enviados: Jueves, 22 de Mayo 2014 8:36:44
Asunto: Re: [lime-dev] I have installed the firmware. Now what? =)
----- Mensaje original -----
> De: "Ramiro Polla" <ramiro.polla(a)gmail.com>
> Para: "libre-mesh developement" <dev(a)lists.libre-mesh.org>
> Enviados: Miércoles, 21 de Mayo 2014 18:43:04
> Asunto: Re: [lime-dev] I have installed the firmware. Now what?
> =)
>
> Hi,
>
> 2014-05-21 6:17 GMT-03:00 Gioacchino Mazzurco
> <gmazzurco89(a)gmail.com>om>:
>> On Tuesday 20 May 2014 23:29:21 Ramiro Polla wrote:
>>> Currently we use OpenWRT+OLSR and a complicated configuration,
>>> I'd
>>> like to replace that with a better and easier to use solution.
>>> I
>>> have
>>> no problem using the command line to connect, but we want more
>>> people
>>> to adopt this, and that way they'd need to do it with a simpler
>>> interface. That's why I thought about using libre-mesh as a
>>> base
>>> system.
>>
>> Yeah you can use this as base system you simply need to develop
>> a
>> lime module
>> that does that for you, start finding a little but meningful
>> name
>> something
>> like lime-* (look at other lime module name for inspiration)
>>
>> And if you can do it by your self with shell of course you will
>> be
>> able to
>> develop a lime module in lua, that integrate with lime ecosistem
>>
>>
>>> So ethernet is shared by default, but how would I configure
>>> another
>>> source for sharing?
>>
>> What you mean by sharing ethernet? If you mean sharing an
>> internet
>> connection
>> available trought ethernet it is in plan but not implemented yet
>
> Hm, I'm confused now. Al says it's supported but you're saying it
> isn't. (I haven't tested yet)
Gioacchino is right. I have supported it in Libre-mesh, but with
justoneclick (guifi.net style[1]), not just by default. Sorry. But
this is planned to be supported by default.
>
>>> (a 3g/4g modem,
>>
>> Yet another module you can implement (I have no time for this
>> now)
>>
>>
>>> another wireless adapter
>>
>> Yet another module you can implement (I have no time for this
>> now)
>>
>>
>>> or even
>>> the same wifi acting as mesh+AP)
>>
>> I doubt this is doable, but it it is, or if i am
>> misunderstanding
>> here it goes
>> the mantra
>
> Mesh+AP+Client works as long as they're on the same channel. (it
> works
> currently with our OLSR setup).
Great, so have no problem to work with MX6+BATMAN-adv setup :)
>
>> Yet another module you can implement (I have no time for this
>> now)
>> ;)
>
> I understand I can add modules to implement things. That is not
> the
> issue. See below.
>
> [...]
>> this is still not implemented yet, so at moment you need to
>> configure manually
>> a node to connect to the internet and annource the default route
>> with bmx6
>
> So it seems that after I get a successful connection, I have to
> announce the default route with bmx6. This is probably what I am
> looking for. Where can I get more information related to this and
> libre-mesh's current setup?
Ok, so if you can get a successful connection for yourself, you
can
announce the default route with bmx6. There's some ways, but I
think
is better that Gioacchino or anybody with more technical
experience
than me, say best way.
That's my /etc/config/lime (i.e. you can change "option
primary_dev"):
----
config lime 'network'
option primary_dev 'eth0'
list vlans '10'
list protos 'bmx6'
list protos 'batadv'
option ipv4_net '192.168.11.0/24'
option ipv6_net '2a00:1508:1:f820::/64'
config lime 'wireless'
option ssid 'garraflliure.guifi.net'
option mesh_bssid 'ca:fe:00:c0:ff:ee'
option mesh_mcast_rate_2ghz '24000'
option mesh_mcast_rate_5ghz '6000'
list mesh_channel_2ghz '11'
list mesh_channel_2ghz '1'
list mesh_channel_5ghz '36+'
----
In uci you have:
lime.network.primary_dev
(and other lime.network.*)
Hey, sorry, also take a look in uci to
bmx6.lm_eth_bmx6=dev
bmx6.lm_eth_bmx6.dev=...
network.wan=interface
network.wan.ifname=...
But wait another answer for a best way :)
When you success manually, we can take a look to think the module
:)
[1] http://ca.wiki.guifi.net/wiki/Unsolclic (sorry catalan only,
summary: list of commands (more or less "automatic generated") to
configure a device just copying & pasting in shell, in this case
(based on OpenWrt) is a list of uci commands).
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
9:59 a.m.
----- Mensaje original -----
De: "Pau" <pau(a)dabax.net>
Para: dev(a)lists.libre-mesh.org
Enviados: Jueves, 22 de Mayo 2014 11:48:24
Asunto: Re: [lime-dev] I have installed the firmware. Now what? =)
Hey al, maybe better than "Nothing to add" is just to add nothing :P
I did it because I was talking about it with a lot of words and you say that you read it
in diagonal. And I wrote it for Ramiro, to say that I agree with you, because before I
said one thing and Gio another one incompatible.
The compatibility between qmp and libremesh is based on:
1. Using the same VLAN tag for the bmx6 network
2. Use the same routing protocol which is bmx6
So once the two networks see each other, they will exchange routes
and
you will be able to reach all nodes.
About "libremesh is fully working", I'm not saying the opposite. But
you
need to set up several things manually (what you actually do with
this
"just-one-click" might be also done from a raw OpenWRT and adding
instructions to install all needed packets),
I don't install extra packages.
which is not what I
understand for a production firmware for building mesh networks.
The mesh network you manage is quite different that a citizens
community
mesh network. You are installing and administration all nodes,
however
in a citizen mesh network the users must install them and manage
them.
To this end, if you want to allow non technical users to do so, you
should provide a set of tools to do it in a easy way. The internet
sharing is an example, but there is also a big need in automatizing
things and the web interface (user does not want and does not know
how
to access throw ssh to the node and execute manual commands).
IMO, libre-mesh will be amazing because the basis architecture is
just
amazing. However there is still a lot of work to do to have a
production
ready firmware (for qMp we have been developing for almost 4 years
and
now we are starting to have a stable-finished version).
I said it before: Ramiro scenario and needs is not a citizen mesh network like in qMp. He
needs dynamic connections outdoor.
Cheers.
On 22/05/14 11:27, al wrote:
----- Mensaje original -----
--
./p4u
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
De: "Pau" <pau(a)dabax.net>
Para: dev(a)lists.libre-mesh.org
Enviados: Jueves, 22 de Mayo 2014 10:26:05
Asunto: Re: [lime-dev] I have installed the firmware. Now what? =)
Hi.
I've been reading this thread in diagonal, so sorry if I repeat
something which has been said. My points are:
1. libiwinfo-lua must be included, we removed the full luci
dependency
some weeks ago to enable only the specific packets, this library
was
missing. Thanks!
Nothing to say.
2. take into account that libre-mesh is in development, which
means
there are many features not yet implemented. As you noticed, the
automatic Internet sharing is one.
Nothing to add.
3. if you want to deploy a production network consider using other
temporal solutions such as http://qmp.cat which will be compatible
with
libre-mesh. However, seems that you have quite good technical
skills,
so
having your contributions in libre-mesh would be very useful.
For me Libre-mesh is fully working. That's it in our 11 nodes in
Jardí Botànic. It's best way when you need connection in outdoor.
That's he needs.
You say that qmp.cat which will be compatible with Libre-mesh.
What's the plan of compatibility?
4. it is completely possible to use a single wifi device as
adhoc+AP
Of course, he said to use the little MR3020 as adhoc+AP+client. And
he said that success. Great!
5. to share Internet connection check the bxm6 documentation (bmx6
-c
tunOut inet /n 0.0.0.0/0 && uci commit)
Nothing to add.
On 22/05/14 08:47, al wrote:
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
----- Mensaje original -----
> De: "al" <al(a)blogmail.cc>
> Para: "libre-mesh developement" <dev(a)lists.libre-mesh.org>
> Enviados: Jueves, 22 de Mayo 2014 8:36:44
> Asunto: Re: [lime-dev] I have installed the firmware. Now what?
> =)
>
>
>
> ----- Mensaje original -----
>> De: "Ramiro Polla" <ramiro.polla(a)gmail.com>
>> Para: "libre-mesh developement" <dev(a)lists.libre-mesh.org>
>> Enviados: Miércoles, 21 de Mayo 2014 18:43:04
>> Asunto: Re: [lime-dev] I have installed the firmware. Now what?
>> =)
>>
>> Hi,
>>
>> 2014-05-21 6:17 GMT-03:00 Gioacchino Mazzurco
>> <gmazzurco89(a)gmail.com>om>:
>>> On Tuesday 20 May 2014 23:29:21 Ramiro Polla wrote:
>>>> Currently we use OpenWRT+OLSR and a complicated
>>>> configuration,
>>>> I'd
>>>> like to replace that with a better and easier to use
>>>> solution.
>>>> I
>>>> have
>>>> no problem using the command line to connect, but we want
>>>> more
>>>> people
>>>> to adopt this, and that way they'd need to do it with a
>>>> simpler
>>>> interface. That's why I thought about using libre-mesh as a
>>>> base
>>>> system.
>>>
>>> Yeah you can use this as base system you simply need to
>>> develop
>>> a
>>> lime module
>>> that does that for you, start finding a little but meningful
>>> name
>>> something
>>> like lime-* (look at other lime module name for inspiration)
>>>
>>> And if you can do it by your self with shell of course you
>>> will
>>> be
>>> able to
>>> develop a lime module in lua, that integrate with lime
>>> ecosistem
>>>
>>>
>>>> So ethernet is shared by default, but how would I configure
>>>> another
>>>> source for sharing?
>>>
>>> What you mean by sharing ethernet? If you mean sharing an
>>> internet
>>> connection
>>> available trought ethernet it is in plan but not implemented
>>> yet
>>
>> Hm, I'm confused now. Al says it's supported but you're saying
>> it
>> isn't. (I haven't tested yet)
>
> Gioacchino is right. I have supported it in Libre-mesh, but with
> justoneclick (guifi.net style[1]), not just by default. Sorry.
> But
> this is planned to be supported by default.
>>
>>>> (a 3g/4g modem,
>>>
>>> Yet another module you can implement (I have no time for this
>>> now)
>>>
>>>
>>>> another wireless adapter
>>>
>>> Yet another module you can implement (I have no time for this
>>> now)
>>>
>>>
>>>> or even
>>>> the same wifi acting as mesh+AP)
>>>
>>> I doubt this is doable, but it it is, or if i am
>>> misunderstanding
>>> here it goes
>>> the mantra
>>
>> Mesh+AP+Client works as long as they're on the same channel.
>> (it
>> works
>> currently with our OLSR setup).
>
> Great, so have no problem to work with MX6+BATMAN-adv setup :)
>>
>>> Yet another module you can implement (I have no time for this
>>> now)
>>> ;)
>>
>> I understand I can add modules to implement things. That is not
>> the
>> issue. See below.
>>
>> [...]
>>> this is still not implemented yet, so at moment you need to
>>> configure manually
>>> a node to connect to the internet and annource the default
>>> route
>>> with bmx6
>>
>> So it seems that after I get a successful connection, I have to
>> announce the default route with bmx6. This is probably what I
>> am
>> looking for. Where can I get more information related to this
>> and
>> libre-mesh's current setup?
>
> Ok, so if you can get a successful connection for yourself, you
> can
> announce the default route with bmx6. There's some ways, but I
> think
> is better that Gioacchino or anybody with more technical
> experience
> than me, say best way.
>
> That's my /etc/config/lime (i.e. you can change "option
> primary_dev"):
> ----
> config lime 'network'
> option primary_dev 'eth0'
> list vlans '10'
> list protos 'bmx6'
> list protos 'batadv'
> option ipv4_net '192.168.11.0/24'
> option ipv6_net '2a00:1508:1:f820::/64'
>
> config lime 'wireless'
> option ssid 'garraflliure.guifi.net'
> option mesh_bssid 'ca:fe:00:c0:ff:ee'
> option mesh_mcast_rate_2ghz '24000'
> option mesh_mcast_rate_5ghz '6000'
> list mesh_channel_2ghz '11'
> list mesh_channel_2ghz '1'
> list mesh_channel_5ghz '36+'
> ----
>
> In uci you have:
> lime.network.primary_dev
> (and other lime.network.*)
Hey, sorry, also take a look in uci to
bmx6.lm_eth_bmx6=dev
bmx6.lm_eth_bmx6.dev=...
network.wan=interface
network.wan.ifname=...
But wait another answer for a best way :)
>
> When you success manually, we can take a look to think the
> module
> :)
>
>
> [1] http://ca.wiki.guifi.net/wiki/Unsolclic (sorry catalan only,
> summary: list of commands (more or less "automatic generated")
> to
> configure a device just copying & pasting in shell, in this case
> (based on OpenWrt) is a list of uci commands).
> _______________________________________________
> Dev mailing list
> Dev(a)lists.libre-mesh.org
> https://lists.libre-mesh.org/mailman/listinfo/dev
>
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
--
./p4u
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
9:57 a.m.
New subject: libiwinfo-lua Was: I have installed the firmware. Now what? =)
On Thursday 22 May 2014 10:26:05 Pau wrote:
1. libiwinfo-lua must be included, we removed the full
luci dependency
some weeks ago to enable only the specific packets, this library was
missing. Thanks!
I believe the right place to add this dependency is lime-webui, or do we use
it in other place too ?
10:06 a.m.
New subject: libiwinfo-lua Was: I have installed the firmware. Now what? =)
I already did it Gio, in lime-webui
Ok Al, nothing else to add then.
On 22/05/14 11:57, Gioacchino Mazzurco wrote:
On Thursday 22 May 2014 10:26:05 Pau wrote:
--
./p4u
1. libiwinfo-lua must be included, we removed the
full luci dependency
some weeks ago to enable only the specific packets, this library was
missing. Thanks!
I believe the right place to add this dependency is lime-webui, or do we use
it in other place too ?
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
7:24 a.m.
New subject: Mesh network for demonstrations (it was: "I have installed the firmware. Now what? =)")
----- Mensaje original -----
De: "Ramiro Polla"
<ramiro.polla(a)gmail.com>
Para: "al" <al(a)blogmail.cc>
CC: "libre-mesh developement" <dev(a)lists.libre-mesh.org>
Enviados: Miércoles, 21 de Mayo 2014 4:29:21
Asunto: Re: [lime-dev] I have installed the firmware. Now what? =)
Hi al,
Hi Ramiro.
[...]
We have a project in Brazil to use Mesh Networks in demonstrations
and
protests to provide a Wireless LAN and Internet to the crowds. There
are people in the crowd with routers using mesh networks extending
the
reach of regular Internet connections that people open up at home.
The
LAN can be used for quick and free communication that does not depend
on 3G or another solution. The routers that are close to Internet
connections are always seeking for new connections. Due to the fact
that the crowd is always walking, we can't connect the nodes to
ethernet.
Currently we use OpenWRT+OLSR and a complicated configuration, I'd
like to replace that with a better and easier to use solution. I have
no problem using the command line to connect, but we want more people
to adopt this, and that way they'd need to do it with a simpler
interface. That's why I thought about using libre-mesh as a base
system.
[...] how would I configure another
source for sharing? (a 3g/4g modem, another wireless adapter, or even
the same wifi acting as mesh+AP)
Ramiro
We're discussing technical issues in original threat, but I also want to recommend
you a socio-technical solution based on demonstrations on Catalonia. I think your proposal
is a good idea because you have not a wireless community network in Brasil yet, but if you
have a little opportunity I strongly recommend you to install fixed routers in buildings
that your community has contacts in center of cities. You can install this routers (or
just one of this routers) by cable to internet and the rest in demostration will be
automatically mesh connected to them. Finally you'll have a permanent infrastructure
to demonstrations, events and for make community and empower local people.
In order to get this solution you can take a look of places proposed to this[1] (we was
drawing it when I was in Brasil).
Contacts that can manage this places and anothers that are not painted yet can be found in
guifi-brasil mailing list[2].
[1] http://map.libre-mesh.org (section Brasil)
[2] https://llistes.guifi.net/sympa/info/guifi-brasil
21 May
21 May
9:10 a.m.
On Wednesday 21 May 2014 00:16:24 al wrote:
Normally we connect router to internet (or to other
network) through
ethernet. Libre-mesh works in that way to default and share this connection
by default.
While this is in plan, because of the big casistic that "sharing internet"
have, and lack of time to discuss/implement at least some of those casistic
this is still not implemented yet, so at moment you need to configure manually
a node to connect to the internet and annource the default route with bmx6
Can not do it in that way? I understand that you are
trying to
use WiFi interface to mesh + AP + client. Is it? I think you can success,
but is strange for me.
It would be one use case of the numerous do discuss on how to implement the in
a extencible and elegant way
About libiwinfo-lua I don't know if is necessary
by default.
It is not inside by default because is not needed but you can compile your own
image with it already in
We make scan
with "iw mesh0 scan", but we don't need it normally, and we don't
want to
offer options that are going to complicate understanding of Libre-mesh (we
are going to delete options). We don't design Libre-mesh to act as a
client, of course you can do it. And we like to hear your needs.
Libre-Mesh is designed to be modular, so you should write a module that does
this automatically for you and integrate it into libremesh ecosystem
Desining stuff in this way will not complicate libre-mesh because being a
module mean you can install it only where you need so no more configuration for
most of the users ;)
3621
days inactive
3623
days old
15 comments
5 participants
participants (5)
-
al -
Gioacchino Mazzurco -
Gioacchino Mazzurco -
Pau -
Ramiro Polla