21 May
2014
21 May
'14
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 ;)