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