Buenas,
Más abajo les envío una presentación que hice hace unos años en la lista de
AlterMesh.
Les cuento que actualmente el proyecto tiene instalados 3 routers wdr3600
en 3 instituciones del Barrio Villa Aguirre, Tandil, pero actualmente no se
provee ningún servicio. Estos equipos los instalaron alumnos de la TUPAR en
el marco de un trabajo de la materia Tecnología de Redes 1.
La versión que tienen instalada los equipos es:
lime-tl-wdr3600-v1-r44952-tandillibre-node-factory.bin
lime-tl-wdr3600-v1-r44952-tandillibre-node-sysupgrade.bin
En este momento en una de las instituciones se está instalando un servidor
que hará de portal cautivo y alojará algunos contenidos (wikipedia,
owncloud). El servidor lo están configurando como trabajo final de la
TUPAR.
Estamos teniendo problemas para lograr que el router otorgue como DNS la ip
de servidor.
Pero si te conectas al wifi y le pones manualmente el DNS (10.233.0.55)
funciona perfecto. (video
<https://drive.google.com/open?id=0BzqwAzOcjbGkYVM2V0xyRFpfYTg>)
Si tienen alguna guía de como configurar el equipo para vincularlo al
servidor de DNS del servidor, nos vendría genial.
También me comentaron los chicos que cuando el equipo pierde la corriente
se borra la configuración. ¿Se les ocurre por que puede ser?
Saludos y gracias!
Santiago
---------- Forwarded message ----------
From: Santi Vallazza <rulosanti(a)gmail.com>
Date: 2015-10-05 14:30 GMT-03:00
Subject: Presentación
To: altermesh(a)listas.altermundi.net
Buenas!
Me presento, mi nombre es Santiago Vallazza, vivo en Tandil, Provincia de
Buenos Aires, Argentina y trabajo en la Facultad de Ciencias Exactas
<http://www.exa.unicen.edu.ar/> de la UNICEN <http://unicen.edu.ar/>. En
esta Facultad tenemos varias carreras, las relacionadas con Sistemas son:
Ingeniería de Sistemas, Tecnicatura Universitaria en Programación y
Administración de Redes (TUPAR) y este año arrancó la Tecnicatura
Universitaria en Desarrollo de Aplicaciones Informáticas (TUDAI).
Soy usuario y militante del Software y la Cultura Libre, hace unos años me
metí en redes pero no pude darle mucha continuidad. Ahora tengo ganas de
retomar el tema.
Ahora estamos con un proyecto que propone crear una red inalámbrica de
alcance barrial, que provea contenidos educativos e informativos. La idea
es poder acceder a contenidos que estén en el servidor del proyecto, que
ubicaremos en una sede de la UNICEN, la Universidad Barrial, y en los
servidores de las escuelas que participen (moodle, etc.).
Del proyecto van a participar algunos estudiantes voluntarios y se
trabajará con docentes y cátedras de Comunicación de Datos de la TUPAR de
Ingeniería de Sistemas, y en ese marco algunos estudiantes realizarán
trabajos de cátedra y de final.
Nos gustó el proyecto Altermundi y el alcance territorial que tiene y el
firmware Altermesh, así que intentaremos usarlo como firmware oficial del
proyecto, y si podemos hacer aportes, también lo haremos. Ya he contactado
a algunos miembros de Altermundi por sus correos personales, pero creo que
este será un medio más apropiados.
Eso es todo por ahora, y en otro hilo comienzo con algunas preguntas.
Saludos!
Santiago
Hi,
I'm trying to go to libremesh.org but I just get this message:
Error. Page cannot be displayed. Please contact your service
provider for more details. (19)
On Thu, 2017-09-07 at 12:15 +0200, ignifugo(a)insicuri.net wrote:
> hi,
Hi!!!
> I did a new pull request in lime-web with the translation of howto.
Saw it, thanks for taking the time to translate the docs!!!
Right now the pull request is waiting for other Italian-speaking
contributors to review (@Ilario and @Gio I guess).
> I'm tring also to do a guide of the web interface of LibreMesh.
>
> This is a first idea:
>
> https://uploads.knightlab.com/storymapjs/b6a9a4c44954565a32b64198c73c
> b6e7/16-lime/index.html
Looks nice... although it is not the main interface I would say.
The interface you are documenting is more related to OpenWRT/LEDE than
LibreMesh... but still it is nice that you are getting involved!
If you want to document an interface that is specific to LibreMesh, you
can check: https://github.com/libremesh/lime-app
I would say it is a production-quality software (thanks to @gmarcos87)
but it hasn't been announced yet.
Regretably, we haven't made any automated builds of the lime-app
package (yet!), so you need to build them from sources.
If you have a router with a recent version of LibreMesh, you can try to
install it by doing:
opkg update
opkg install lime-webui-ng-luci
opkg install lime-app
It is still work-in-progress... so YMMV.
> the problem for me is that doc is not to improve, but to write, and
> I'm
> not enough in deep to do these.
Yes... it is defiinitely a different challenge... but a good one if you
want to learn more about LibreMesh.
What do you want to accomplish? Maybe having that clear helps you and
the community to know what you can do :)
>
> Can someone help me.
Hi! I was able install Lime_mini in tl-wa701n, but can't link to other
Lime over tl-wdr3500. Is my first association with Mesh nodes.
(Thank Ilario for you help for instalation! I am not know what happened
with thanks mail. I'm sure I wrote it because of my difficulty with
English :-)
In the Lime config files of both routers, are different in "lime config
wifi/list modes". They are not visible.
If in both write 'adhoc', i only see wa701 from wdr3500.
if in both i write 'ieee80211s', see nothing.
Does this influence to associate them? Are different branch.
Thank newly.
Seba
----------------------
Model TP-Link TL-WDR3500 v1
Versión del firmware LEDE Reboot 17.01.1 r3316-7eb58cf109 / LuCI
lede-17.01 branch (git-17.152.82987-7f6fc16)
/etc/config/lime is:
config lime 'system'
option hostname 'LiMe-%M4%M5%M6'
option domain 'lan'
config lime 'network'
list protocols 'adhoc'
list protocols 'lan'
list protocols 'anygw'
list protocols 'batadv:%N1'
list protocols 'bmx6:13'
list protocols 'olsr:14'
list protocols 'olsr6:15'
list protocols 'olsr2:16'
option primary_interface 'eth0'
list resolvers '4.2.2.2'
list resolvers '141.1.1.1'
list resolvers '2001:470:20::2'
option main_ipv4_address '10.%N1.0.0/16'
option main_ipv6_address '2a00:1508:0a%N1:%N200::/64'
option bmx6_over_batman 'false'
option bmx6_mtu '1398'
config lime 'wifi'
list modes 'ap'
list modes 'apname'
list modes 'ieee80211s'
option adhoc_mcast_rate_5ghz '6000'
option ap_ssid 'LibreMesh.org'
option ieee80211s_mesh_id 'LiMe'
option ieee80211s_mesh_fwding '0'
option apname_ssid 'LibreMesh.org/%H'
option adhoc_bssid 'ca:fe:00:c0:ff:ee'
option htmode_5ghz 'HT40'
option channel_2ghz '11'
option adhoc_mcast_rate_2ghz '24000'
option channel_5ghz '48'
option adhoc_ssid 'LiMe'
config net 'lm_hwd_openwrt_wan'
option autogenerated 'true'
list protocols 'adhoc'
list protocols 'anygw'
list protocols 'batadv:%N1'
list protocols 'bmx6:13'
list protocols 'olsr:14'
list protocols 'olsr6:15'
list protocols 'olsr2:16'
list protocols 'wan'
option linux_name 'eth1'
--------------------------
Model TP-Link TL-WA701N/ND v1
Versión del firmware LiMe develop development (develop rev.3ba372f
20170823_1516) / LuCI lede-17.01 branch (git-17.232.21093-079f65a)
/etc/config/Lime is:
config lime 'system'
option hostname 'LiMe-%M4%M5%M6'
option domain 'lan'
config lime 'network'
option primary_interface 'eth0'
list resolvers '4.2.2.2'
list resolvers '141.1.1.1'
list resolvers '2001:470:20::2'
list protocols 'ieee80211s'
list protocols 'lan'
list protocols 'anygw'
list protocols 'batadv:%N1'
list protocols 'bmx6:13'
list protocols 'olsr:14'
list protocols 'olsr6:15'
list protocols 'olsr2:16'
option main_ipv4_address '10.%N1.0.0/16'
option main_ipv6_address '2a00:1508:0a%N1:%N200::/64'
option anygw_mac 'aa:aa:aa:%N1:%N2:aa'
option bmx6_pref_gw 'none'
option bmx6_over_batman 'false'
option bmx6_mtu '1500'
config lime 'wifi'
list modes 'ap'
list modes 'apname'
list modes 'adhoc'
option ieee80211s_mesh_id 'LiMe'
option adhoc_mcast_rate_5ghz '6000'
option ap_ssid 'LibreMesh.org'
option distance '1000'
option ieee80211s_mesh_fwding '0'
option apname_ssid 'LibreMesh.org/%H'
option adhoc_bssid 'ca:fe:00:c0:ff:ee'
option htmode_5ghz 'HT40'
option channel_2ghz '11'
option adhoc_mcast_rate_2ghz '24000'
option channel_5ghz '48'
option adhoc_ssid 'LiMe'
---------------
Hello! I continue to learn about LiMe, now using SDK. I cooked the image
for a tl-wa701nd v1 because it does not exist in the image repository.
But I do not know which file I should upload. The files in
lime-sdk/output/ar71xx/generic/tl-wa701nd-v1/lime_default/ are:
lede-17.01.1-libremesh-ar71xx-generic-device-tl-wa701nd-v1.manifest
lede-17.01.1-libremesh-ar71xx-generic-root.squashfs
lede-17.01.1-libremesh-ar71xx-generic-uImage-lzma.bin
lede-17.01.1-libremesh-ar71xx-generic-vmlinux.bin
lede-17.01.1-libremesh-ar71xx-generic-vmlinux.elf
lede-17.01.1-libremesh-ar71xx-generic-vmlinux.lzma
lede-17.01.1-libremesh-ar71xx-generic-vmlinux-lzma.elf
sha256sums
I look for ... squashfs-factory.bin but it is not. Then I do not know
where to migrate the firmware.
The * vmlinux * discard them because they are virtual images for a
simulation. Right?
I like .squashfs but it's not .bin
UImage-lzma.bin remains. Is this to do it from OEM?
I am looking in the right directory?
Should I use a form other than oem?
The docs of openwrt have helped me but now I do not see the way :-)
Thanks for the help.
So I've built Libremesh using the sdk for my wrt54gs v3. It boots fine, but the wireless is not working by default. Should I have to do extra configuration? I did notice both ad-hoc and 80211s are on by default.
McL0v1n
hello there,
we try to setup different customized lime installations for a camp.
our routers: tplink 4300.
1) the following configuration is working for ap encryption but not for
the mesh:
* cooking in branch stable (we also tried develop with the latest
working commit):
V=s J=1 ./cooker -c ar71xx/generic --flavor=lime_camp
--profile=tl-wdr4300-v1 --community=camp/commoniee80211s
* flavors.config
lime_camp="lime-full -dnsmasq -wpad-mini wpad authsae"
* etc/config/lime_defaults:
config lime system
option hostname 'CA-%M4%M5%M6'
option domain 'mesh.camp.local'
option keep_on_upgrade 'libremesh base-files-essential
/etc/sysupgrade.conf'
config lime network
option primary_interface eth0
option main_ipv4_address '10.5.0.0/21'
option main_ipv6_address '2801:01e8:2::/64'
option bmx6_mtu '1500'
list protocols ieee80211s
list protocols lan
list protocols anygw
list protocols batadv:%N1
list protocols bmx6:13
list protocols olsr:14
list protocols olsr6:15
list protocols olsr2:16
list resolvers 4.2.2.2 # b.resolvers.Level3.net
list resolvers 141.1.1.1 # cns1.cw.net
list resolvers 2001:470:20::2 # ordns.he.net
option bmx6_over_batman false
option bmx6_pref_gw none
option bmx7_over_batman false
option anygw_mac "aa:aa:aa:%N1:%N2:aa"
config lime wifi
option channel_2ghz '11'
option channel_5ghz '48'
option htmode_5ghz 'HT40'
list modes 'ap'
list modes 'apname'
list modes 'ieee80211s'
option ap_ssid 'Unsecure'
option apname_ssid 'Unsecure | %H'
option adhoc_ssid 'Mesh | Camp'
option adhoc_bssid '16:27:F6:27:57:14'
option adhoc_mcast_rate_2ghz '24000'
option adhoc_mcast_rate_5ghz '6000'
option ieee80211s_mesh_fwding '0'
option ieee80211s_mesh_id 'Mesh_Camp'
option ap_encryption 'psk2+ccmp'
option ap_key 'somepassword'
option apname_encryption 'psk2+ccmp'
option apname_key 'somepassword'
2) if we add to the "config lime wifi"
option ieee80211s_encryption 'psk2+ccmp'
option ieee80211s_key 'someotherpassword'
the mesh disappears.
are there other packages we still need to get it working besides "wpad"
& "authsae" or is there anything else we are missing?
thank you!
Hi all
I've finally had the chance to test out what some of you were saying about LiMe doing mesh over ethernet using Lan - to - Lan connections.
I have a POE switch with one cable going to a UBNT AC lite, one going to a Bullet M2, one going to a 1043ND [on its wan port] and one to an Archer C7 [on its wan port]. All 4 devices have the latest images downloaded from repo.libremesh.org, just to be on the safe side. The fifth cable is going to my ISP router [IP 192.168.111.1].
Since the lite and the bullet only have one ethernet port, stock lime configures it as a Lan port, with 10.13.0.x DHCP being handed out over it, and so on. So from the switch I have two cables going to wan ports [1043 and C7] and two going to "Lan" ports [lite and bullet] since that's what their default behavior is.
They all mesh correctly, and even the two UBNTs serve internet connectivity perfectly. The problem is that when I connect to these two devices wirelessly with clients, I often get a DHCP assignment from my ISP router [as it's on the 192.168.111.x subnet] and not a 10.13.0.x assignment.
I still don't understand how a network with not one, but several DHCP servers can work correctly. I seem to understand that LiMe can ignore such advertisements on its Lan ports, but what happens to a client that is on such wired network, say, with another cable from the switch I mentioned? Won't he receive advertisements from all servers at once? Does LiMe terminate advertisements upstream-bound when it detects others?
And in the case of the 1043 and C7 that are using their wan ports, how does LiMe understand when it should mesh with other devices over it and when it should become a DHCP client to an upstream non-mesh router in a traditional way?
And how do I solve this DHCP leaking from ISP router to LiMe routers' clients in the case of the lite and bullet?
Thank you in advance
Nk
On 08/05/2017 11:23 PM, Patricio Gibbs wrote:
> On 08/04/2017 07:47 PM, Ilario Gelmetti wrote:
>> On 08/05/2017 01:41 AM, Patrick Patricio Gibbs wrote:
>>> Two scenarios in which we want to control access based on set
>>> schedules. Ideally this would be configured in the luci GUI.
>>>
>>> A) Router WiFi Schedule
>>> Faby has a router with LibreMesh in her house, and she wants the WiFi
>>> to turn on every day at 2pm and turn off at 6pm. This could be
>>> achieved a number if ways:
>>> - the WiFi radios are enabled only during the desired hours.
>>
>> To switch on and off the radio sounds the easiest way to me.
>> Just adding to cron a line to switch it off using "wifi off radio0"
>> (also a line for radio1 also if the router is also 5 GHz) at 6pm and
>> another line to switch it on again with "wifi radio0" at 2pm should be
>> enough. And if you unexpectedly need the AP to be on out of allowed
>> hours you just reboot the router (unplug and plug) and the AP will be
>> active again.
>
> Any chance of getting a GUI version of this that persists between reboots?
Err, this would be something to implement on LEDE/OpenWrt side, in my
opinion.
You can find many related links on this page:
https://forum.lede-project.org/t/scheduling-on-off-wifi/3385
For example there's a luci-app-wifischedule package you can install on
LibreMesh and try :)
Let us know!
Ilario
