Hi,
Could somehow a LiMe router connect as a client to an external Wi-Fi
network and use that connection as a WAN?
I mean a LiMe router joining -as a station- a third-party AP (in
infrastructure mode), use that connection as a WAN, and keeping every
LiMe feature.
Is that possible?
If it is, and it is easily configurable,
how would you do it?
Hi,
Here we have been running 16.07,
it is the time now to go for 17.07.
I never compile anything,
but as Chef is not there yet,
I am trying to build and cook.
Please be patient with my questions...
I followed the "Cook your own firmware using lime-sdk" section
at http://libremesh.org/getit.html
and now I am following the instructions at
https://github.com/libremesh/lime-sdk/blob/master/README.md
My computer runs Trisquel 7, it's based on Ubuntu 14.04.
When doing ./cooker -b ar71xx/generic
I get the following:
...
make -r world: build failed. Please re-run make with -j1 V=s to see
what's going on
make: *** [world] Error 1
make: Leaving directory `/home/fone/lime-sdk/17.01.2/ar71xx/generic/sdk'
-> Error compiling SDK
amuza@compu:~/lime-sdk$
When trying to run this recommended "make with -j1 V=s"
this is what I get:
amuza@compu:~/lime-sdk$ make with -j1 V=s
make: *** No rule to make target `with'. Stop.
amuza@compu:~/lime-sdk$
Any basic help is gratefully welcome!
Hello Here,
Any Idea on this ??
thanks
"A Goal is a Dream with a Plan and a Dateline"
Do On to Others what you will like them to do on to you.'The Golden Rule'
The CEO of ABEBOH
Computer Software Engineering Student
Music DJ . Artiste at Casky Black's Record
Regional Coordinator and CAC Member at Mozilla Campus Club Program.
On Wed, Oct 18, 2017 at 1:11 PM, Nges B <nges.brian(a)gmail.com> wrote:
> That is a short on screen video showing how the box is not connect
>
> "A Goal is a Dream with a Plan and a Dateline"
> Do On to Others what you will like them to do on to you.'The Golden Rule'
> The CEO of ABEBOH
> Computer Software Engineering Student
> Music DJ . Artiste at Casky Black's Record
> Regional Coordinator and CAC Member at Mozilla Campus Club Program.
>
>
> On Wed, Oct 18, 2017 at 12:38 PM, Nges B <nges.brian(a)gmail.com> wrote:
>
>> Hello sorry for the error. Yeah I am talking of http://thisnode.info
>> it does not connect. the greatest thing is that the router does not
>> connect to the computer. It keeps trying to connect forever.
>>
>>
>>
>> "A Goal is a Dream with a Plan and a Dateline"
>> Do On to Others what you will like them to do on to you.'The Golden Rule'
>> The CEO of ABEBOH
>> Computer Software Engineering Student
>> Music DJ . Artiste at Casky Black's Record
>> Regional Coordinator and CAC Member at Mozilla Campus Club Program.
>>
>>
>> On Wed, Oct 18, 2017 at 10:51 AM, Ilario Gelmetti <iochesonome(a)gmail.com>
>> wrote:
>>
>>> On 10/18/2017 09:56 AM, Nges B wrote:
>>> > The flashing process took more than 8hours which was unusual to me so I
>>> > terminated the process.
>>>
>>> You've done well, for sure the flashing was finished after less than 5
>>> minutes.
>>>
>>> > All the first points are correct. I need to connect to the router but
>>> > thenode.info <http://thenode.info> can not connect.
>>>
>>> The address is http://thisnode.info and not "the" as you wrote, does
>>> this work?
>>> Try connecting only to the router, either via cable disabling the
>>> wireless on your laptop or via wireless not connecting to anything else
>>> via cable.
>>>
>>>
>>> _______________________________________________
>>> lime-users mailing list
>>> lime-users(a)lists.libremesh.org
>>> https://lists.libremesh.org/mailman/listinfo/lime-users
>>>
>>
>>
>
Hi, Patrick/Patricio/Pato here, coordinating the translation of the software and documentation related to the LibreRouter. I write to the list to let folks know what's going on and open for feedback about the current plan.
After considering various options of what platform to use for translation management, I think the most appropriate is TranslateWiki.net, because it means:
- someone else takes care of the hosting,
- is costs us no money (though we could donate some if they need it and if our budget allows),
- we share the platform with other open source software projects,
- we join a platform that already has an active community of translators in many languages,
- the software running the platform is stable and has been in production use to translate the MediaWiki interface for some time,
- and all of that together means that once we get our process with TranslateWiki.net going well, it could run easily for years and allow the addition of new languages easily.
Joining TranslateWiki.net requires giving direct push commit access to at least one TranslateWiki.net admin, so that new translations get committed quickly and thus new translations make it into software releases as quickly as practical.
I hope that we can get a relationship with TranslateWiki.net setup and translation underway before the end of October, so if you have any ideas, questions, objections, please respond in the next few days.
[A shortcoming of TranslateWiki.net is that it can't handle ODT files, which is the current format for the documentation booklets. We'll either find a way to convert the booklet text into a compatible format, or we'll use a different tool (perhaps Zanata) that works well with the current creation process of the booklets. More about documentation translation in another email.]
For those curious about TranslateWiki.net, see this page
https://translatewiki.net/wiki/Translating:New_project
For those who want to understand i18n and l10n from a software development perspective (that's internationalization and localization), see:
https://translatewiki.net/wiki/Translating:Localisation_for_developers
*Developers, please read that, at least a little.*
To see our conversation so far with TranslateWiki.net:
https://translatewiki.net/wiki/Support#LibreRouter:_new_project_with_softwa…
Once a software has an i18n and l10n structure setup, we add a "qqq" language file for the documentation about each string that will be translated. More details about that here:
https://www.mediawiki.org/wiki/Localisation#Message_documentation
SOFTWARE:
LibreMesh uses Gettext, and is translated into Spanish:
https://github.com/libremesh/lime-packages/blob/develop/packages/lime-webui…
LimeApp uses a JSON format, and is translated into Spanish:
https://github.com/libremesh/lime-app/tree/master/i18n/translations
Firmware Chef uses Gettext, and is translated into Spanish:
https://github.com/libremesh/alterchef/tree/master/altermeshfc/altermeshfc/…
I haven't yet found the locations of the translation files for the following software, or confirmed whether the software even has translation files:
- LibreMap
https://github.com/libremap
- WiFi Calling (app and server)
-- repository unknown
- LimeBuild / Cooker / SDK
https://github.com/libremesh/lime-sdk
- LibreNet6
-- repository unknown
- Pitbull captive portal
https://github.com/libremesh/pitbull
- LibreServer (more complex since it's an entire GNU/Linux distro, though maybe there's a central admin interface)
-- repository unknown
Over the long term, we might consider changing the i18n/l10n format of some of the software to a format preferred by TranslateWiki.net, as described in this note from TranslateWiki.net:
"Use of key-based file formats is preferred, like Java properties and Ruby-style YAML. Other supported file formats are PHP arrays, PHP variables and Gettext." For now, making such a change is not priority and probably not within our capacity. Pau pointed out to me that in LibreMesh, there's a little program that pulls strings out of the code and puts them in the translation files, and that a similar function would be necessary if we changed to a different format. We could ask at TranslateWiki.net if they know of such programs.
~ Patrick
never mind, I was using the old lime-config on the profile...
On Thu, Oct 19, 2017 at 9:39 PM, bruno vianna <bruno(a)pobox.com> wrote:
> hi
>
> i'm trying to flash a few tp-link wr471nd with the latest lime.
> when i use the pre-compiled bin, it works fine:
> http://downloads.libremesh.org/releases/17.06/targets/
> ar71xx/generic/tl-wr741nd-v4/lime_mini/lede-17.01.2-lime-
> mini-ar71xx-generic-tl-wr741nd-v4-squashfs-factory.bin
>
> but if I cook with new jefe, it flashes but doesn't work - no wifi and
> even ethernet won't get me an ip number. I actually have to do the failsafe
> recovery everytime with this:
> https://betaupdate.libremesh.org/static/lime/17.06/ar71xx/
> generic/tl-wr741nd-v4/b7a7a95beb0a077/lime-17.06-b7a7a95beb0a077-ar71xx-
> generic-tl-wr741nd-v4-sysupgrade.bin
>
> same thing happens when use the cooker script. any ideas?
>
> thanks
> bruno
> --
>
> bruno(a)pobox.com ▀─█▄██▄▀▄
> http://brunovianna.net ─█▄██▄▀█▀█▄
> skype: randomico▀─█▄██▄▀█▀█▄▌██─█▌█▌
>
>
>
>
--
bruno(a)pobox.com ▀─█▄██▄▀▄
http://brunovianna.net ─█▄██▄▀█▀█▄
skype: randomico▀─█▄██▄▀█▀█▄▌██─█▌█▌
Hello all, I am trying to cook the Firmware of of the LibreRouter for
TP-link3600.
I have followed the instructions as on https://github.com/libremesh/lime-sdk
I have build the firmware but I cant cook it. I have had the error Build
dependency: Please install ncurses. (Missing libncurses.so or ncurses.h)
and I have done all sorts of manipulations to get ncurses installed but I
have not succeeded since yesterday.
I am working with Ubuntu 15.10
Please any Idea or help on this is appreciated.
Thanks and waiting to hear from you
At your service
nges Brian
"A Goal is a Dream with a Plan and a Dateline"
Do On to Others what you will like them to do on to you.'The Golden Rule'
The CEO of ABEBOH
Computer Software Engineering Student
Music DJ . Artiste at Casky Black's Record
Regional Coordinator and CAC Member at Mozilla Campus Club Program.c DJ .
Artiste at Casky Black's Record
Regional Coordinator and CAC Member at Mozilla Campus Club Program.
Hi guys, apologize for reorganizing this conversation again. I think it
is better for it to have its own thread.
So, to recap, the conversation comes from the thread "Recommended
devices?":
Patricio Gibbs on 07/27/2017
The conversation in this thread has documented some useful knowledge.
Is there a place to compile this information in a list of
compatible devices?
I see the mostly empty list at:
http://libremesh.org/docs/hardware/
Such a list could be part of a guide about how to choose a device,
or how to guess whether a device might work or is definitely
unsupported.
Bruno Vianna on 07/29/2017
I like the idea too, but it would be much easier if it were a wiki or
some kind of editable page.
I contribute to openwrt's wiki every time when I find out info on a new
device.
I understand the content from libremesh is in github, but it is a lot
more bureaucratic to edit the html, push it, wait for merge...
So, dear libremesh site managers, do you think we can have a wiki or
some open content solution?
We talked with Gui/Gio/Pau/NicoE about this and think that would like
to make a decision that reinforces the community, so instead of pushing
a specific implementation, it is better to share our perspectives on
the subject and consider experimenting something a bit in the way to
the "advice process" http://www.reinventingorganizationswiki.com/Decisi
on_Making, which we are implementing as:
someone who is in a good/the best place to make this decision (can mean
many things but let's consider responsible for implementing and
maintaining, and accountable for the results... who would be me so far)
will lead an "advice process" which means receiving advice from all
those who can have relevant contributions and/on will be affected by
it, meaning you.
So this is a brief of the points of that group, which I'll share since
I consider valuable for all to know them:
Pro "current state"
We left RedMine because it was not working, people was not contributing
and the info was not being updated. Now that it is more code-related
the info is kept in a more coherent way.
On GitHub there is the "Edit" button.
It is not necessarilly bad to have to wait for a Pull Request to be
accepted.
Pro "Wiki"
Now we are a bigger communitty, how do we enhance involvement?
We can make a monthly test with the GitHub wiki with the unnoficial
info like "experiences with hw", "specific tutorials", "cases" and so.
The downside of the github wiki is that it can only be editted by
collaborators of the repository.
So based on this information, which key points would be relevant to
consider to move forwards?
Please share your points of view so we move on to have a definition.
As said, it is an experiment of using a decision making method which
seemed to us can be a good one for the kind of community we work to
build. Please then shared also your feedback about this.
Part of this process has been promoted by a relative new member of the
community (5 months or so), Rodrigo Monelos, who has been mainly acting
as facilitator and Agile coach on the LibreRouter project, so he will
be helping also with the coordination of it.
I hope he can introduce himself to come out of the shadows :)
Regards,
Hola!
Les escribo por que precisamente tengo el mismo problema con la asignación
de servidor dns.
A continuación les paso a detallar la conexion de los equipos en cuestión,
en una computadora con una distribución basada en Debian esta instalado un
servidor dns con bind9, y otros servicios como un Owncloud, una web
institucional, etc; Ese servidor está conectado a un puerto Lan (ip fija)
de un router con Openmesh.
La idea de asignar un servidor dns por el momento solo cumpliria con el
objetivo de que todo usuario que se conecte a la red tenga que pasar por un
portal cautivo, por lo cual el servidor dns con cualquier url devuelve la
ip del servidor.
Si en las propiedades de conexión de los equipos defino el servidor dns con
la ip del equipo en el cual esta instalado, el portal cautivo funciona.
Realice las siguientes pruebas sin conseguir el resultado esperado:
1) En la interfaz web en el apartado de DHCP borre todos los servidores dns
por defecto y dejé solo la dirección del servidor de la red local.
2) Modifique el archivo de configuración de Lime y ejecuté el comando
lime-config, luego revisé si se propagaron los cambios a los otros archivos
de configuración y los cambios en la configuración efectivamente se
propagaban al resto de los archivos.
3) En el router instalé el paquete nodogsplash para probar otro método para
cumplir con el objetivo del portal cautivo, seguí los pasos de
configuración de diferentes guías y no logre que funcione.
4) no pude modificar el /etc/resolv.conf, cree un nuevo archivo fuera de la
carpeta /tmp al que hago referencia desde el /etc/config/dhcp con la ip del
servidor dns.
Por lo cual me quedan las siguientes preguntas:
¿Como debería realizar la configuración para que se asignen los servidores
dns a los clientes, o en su defecto lograr objetivo similar?
¿Esta bien conectar el servidor al puerto Lan o debería conectar el mismo
al puerto Wan del router?
¿Las configuraciones para la red mesh debería aplicarla a todos los
servidores?
Disculpen la extensión del mensaje, ante todo agradezco por adelantado que
me puedan llegar a orientar.
Saludos!
El 29 de septiembre de 2017, 17:21, Santi Vallazza <rulosanti(a)gmail.com>
escribió:
>
> ---------- Forwarded message ----------
> From: Gui Iribarren <gui(a)altermundi.net>
> Date: 2017-09-22 15:24 GMT-03:00
> Subject: Re: [lime-users] Fwd: Presentación
> To: lime-users(a)lists.libremesh.org
>
>
> On 22/09/17 18:21, Santi Vallazza wrote:
> > reinstalamos el firmware y ahora guarda los cambios.
> >
> > Volviendo al tema original:
> >
> > Aún no pudimos hacer que el router asigne como DNS a los clientes la
> > dirección IP de nuestro servidor.
> >
> > ¿Pueden indicarnos en qué archivo deberíamos realizar esa configuración?
>
> /etc/config/lime
>
> veras en
> config lime 'network'
> list resolvers '4.2.2.2'
> list resolvers '141.1.1.1'
> list resolvers '2001:470:20::2'
>
> reemplaza esas 3 lineas por 1 sola q diga
> list resolvers '1.2.3.4'
> (o sea, la ip de vuestro servidor)
>
> y luego corre 'lime-config'
>
> ( detras de escena, eso se "propaga" hacia...
> /etc/config/dhcp
> q a su vez terminan siendo lineas en
> /var/etc/dnsmasq.conf.cfg* )
>
> vale decir que, en los clientes el servidor DNS seguira siendo el router
> libremesh (que corre dnsmasq), pero dnsmasq del router libremesh
> forwardeara todos los pedidos hacia vuestro servidor deseado
>
> >
> > Gracias!
> >
> > El 1 sept. 2017 6:40 a. m., "Gui Iribarren" <gui(a)altermundi.net
> > <mailto:gui@altermundi.net>> escribió:
> >
> > On 01/09/17 10:50, Nicolás Echániz wrote:
> > > On 08/31/2017 12:04 PM, Santi Vallazza wrote:
> > >> Buenas!
> > >>
> > >> El routers es un wdr3600
> > >>
> > >> La versión que tienen instalada los equipos es:
> > >> lime-tl-wdr3600-v1-r44952-tandillibre-node-factory.bin
> > >
> > > Santi, de dónde descargaste ese .bin?
> >
> > sospecho que de aqui
> >
> > https://chef.altermundi.net/ls/tandillibre/r44952/node/ar71
> xx/openwrt-tl-wdr3600-v1-r44952-tandillibre-node-factory.bin
> > <https://chef.altermundi.net/ls/tandillibre/r44952/node/ar7
> 1xx/openwrt-tl-wdr3600-v1-r44952-tandillibre-node-factory.bin>
> >
> > y es identico al release
> > https://chef.altermundi.net/diff/tandillibre-node/libre-mesh-1509/
> > <https://chef.altermundi.net/diff/tandillibre-node/libre-mesh-1509/>
> >
> > por lo tanto no me queda otra explicacion que un fallo de hardware???
> > onda que la flash tenga un error y la monte como readonly?
> >
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > lime-users mailing list
> > > lime-users(a)lists.libremesh.org <mailto:lime-users@lists.libre
> mesh.org>
> > > https://lists.libremesh.org/mailman/listinfo/lime-users
> > <https://lists.libremesh.org/mailman/listinfo/lime-users>
> > >
> >
> >
> > _______________________________________________
> > lime-users mailing list
> > lime-users(a)lists.libremesh.org <mailto:lime-users@lists.libre
> mesh.org>
> > https://lists.libremesh.org/mailman/listinfo/lime-users
> > <https://lists.libremesh.org/mailman/listinfo/lime-users>
> >
> >
> >
> > _______________________________________________
> > lime-users mailing list
> > lime-users(a)lists.libremesh.org
> > https://lists.libremesh.org/mailman/listinfo/lime-users
> >
> _______________________________________________
> lime-users mailing list
> lime-users(a)lists.libremesh.org
> https://lists.libremesh.org/mailman/listinfo/lime-users
>
>
