22 May
2014
22 May
'14
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