Hi all!
Here in Hackmeeting-it [1] we reflashed every router in the original
network setup with LibreMesh :D
We used unstable image taken from repo.libremesh.org using 802.11s and
up to now works perfect with 30 clients :D
Bye!
Ilario
[1] https://hackmeeting.org/hackit17/
Hi all! Sorry for the very brief OT. I've finally arrived at Hackmeeting and I'm seeing a whole lotta LiMe networks! Among you who all is here? It'd be so cool to actually meet you finally ;]
Thanks in advance!
Nk
________________________________
From: bruno vianna <bruno(a)pobox.com>
Sent: Jun 17, 2017 3:58 PM
To: libremesh users
Subject: Re: [lime-users] Hackmeeting-it
What a mix!
On Fri, Jun 16, 2017 at 10:58 PM, Ilario Gelmetti <iochesonome(a)gmail.com> wrote:
> We're using TP-Link WDR3600, TP-Link WDR4300, Ubiquiti NanoStation M5
> XW, Ubiquiti NanoStation M5 LoCo XM, Ubiquiti NanoStation M2 XW, Unifi
> AP AC LR (yes, it's working! But the flashing procedure has to be
> carefully followed), TP-Link CPE220, TP-Link WR1043ND v4
>
> I was willing to try to compile also for TP-Link WDR4900 (which is not
> currently in the lime-sdk available profiles) but lime-sdk has some new
> problem. Seems like a compatibility issue between old version of
> libwebsockets and a new version of cyassl/wolfssl, used by the new LiMe
> web interface...
>
> On 06/16/2017 10:02 PM, bruno vianna wrote:
>> Which routers are you using?
>>
>> Em 16 de jun de 2017 4:20 PM, "Ilario Gelmetti" <iochesonome(a)gmail.com
>> <mailto:iochesonome@gmail.com>> escreveu:
>>
>> The graph is a screenshot from the LuCI web interface of the routers,
>> you can find it in the BMX6/Graph menu :)
>>
>> The number "30" were the clients, I meant smartphones and laptops (now
>> the number increased). I don't know if there's a graph including those.
>> I _suppose_ it can be obtained using batadv-vis.
>> https://www.open-mesh.org/projects/alfred/wiki/Batadv-vis
>> <https://www.open-mesh.org/projects/alfred/wiki/Batadv-vis>
>> But when I try to use it I get an error:
>>
>> # batadv-vis -s
>> can't connect to unix socket: Connection refused
>>
>> Now we're going to deploy 4-6 more routers for covering more area.
>>
>>
>>
>> On 06/16/2017 08:42 PM, Paul Spooren wrote:
>> > Aw snap, I mean picture :)! Was it auto created?
>> > It just shows 4 nodes, do you have a picture of the full setup with 30
>> > nodes?
>> >
>> > Thanks!
>> >
>> > On 16.06.2017 20:40, Ilario Gelmetti wrote:
>> >> Hey!
>> >> I didn't, as I wrote in the email I downloaded the image from
>> >> repo.libremesh.org <http://repo.libremesh.org>
>> >> When I try to compile it with lime-sdk I'm having problems:
>> >>
>> >> make[3] -C
>> /home/ilario/software/lime-sdk/feeds/limeui/libwebsockets compile
>> >> make -r world: build failed. Please re-run make with -j1 V=s to see
>> >> what's going on
>> >> make: ***
>> >>
>> [/home/ilario/software/lime-sdk/17.01.2/ar71xx/generic/sdk/include/toplevel.mk:193
>> <http://toplevel.mk:193>:
>> >> world] Error 1
>> >>
>> >> cd 17.01.2/ar71xx/generic/sdk
>> >> make -r world
>> >>
>> >> make[3]: Entering directory
>> >> '/home/ilario/software/lime-sdk/feeds/limeui/libwebsockets'
>> >> if [ -f
>> >>
>> /home/ilario/software/lime-sdk/17.01.2/ar71xx/generic/sdk/staging_dir/target-mips_24kc_musl-1.1.16/pkginfo/libwebsockets.cyassl.install.clean
>> >> ]; then rm -f
>> >>
>> /home/ilario/software/lime-sdk/17.01.2/ar71xx/generic/sdk/staging_dir/target-mips_24kc_musl-1.1.16/pkginfo/libwebsockets.cyassl.install
>> >>
>> /home/ilario/software/lime-sdk/17.01.2/ar71xx/generic/sdk/staging_dir/target-mips_24kc_musl-1.1.16/pkginfo/libwebsockets.cyassl.install.clean;
>> >> fi
>> >> mkdir -p
>> >>
>> /home/ilario/software/lime-sdk/17.01.2/ar71xx/generic/sdk/bin/targets/ar71xx/generic/packages
>> >>
>> /home/ilario/software/lime-sdk/17.01.2/ar71xx/generic/sdk/build_dir/target-mips_24kc_musl-1.1.16/libwebsockets-0c7e5a94182b8bf5b5be2fc58141466bf54d5812/ipkg-mips_24kc/libwebsockets-cyassl/CONTROL
>> >>
>> /home/ilario/software/lime-sdk/17.01.2/ar71xx/generic/sdk/staging_dir/target-mips_24kc_musl-1.1.16/pkginfo
>> >> install -d -m0755
>> >>
>> /home/ilario/software/lime-sdk/17.01.2/ar71xx/generic/sdk/build_dir/target-mips_24kc_musl-1.1.16/libwebsockets-0c7e5a94182b8bf5b5be2fc58141466bf54d5812/ipkg-mips_24kc/libwebsockets-cyassl/usr/lib
>> >> cp -fpR
>> >>
>> /home/ilario/software/lime-sdk/17.01.2/ar71xx/generic/sdk/build_dir/target-mips_24kc_musl-1.1.16/libwebsockets-0c7e5a94182b8bf5b5be2fc58141466bf54d5812/ipkg-install/usr/lib/libwebsockets.so*
>> >>
>> /home/ilario/software/lime-sdk/17.01.2/ar71xx/generic/sdk/build_dir/target-mips_24kc_musl-1.1.16/libwebsockets-0c7e5a94182b8bf5b5be2fc58141466bf54d5812/ipkg-mips_24kc/libwebsockets-cyassl/usr/lib/
>> >> find
>> >>
>> /home/ilario/software/lime-sdk/17.01.2/ar71xx/generic/sdk/build_dir/target-mips_24kc_musl-1.1.16/libwebsockets-0c7e5a94182b8bf5b5be2fc58141466bf54d5812/ipkg-mips_24kc/libwebsockets-cyassl
>> >> -name 'CVS' -o -name '.svn' -o -name '.#*' -o -name '*~'| xargs
>> -r rm -rf
>> >> Package libwebsockets-cyassl is missing dependencies for the
>> following
>> >> libraries:
>> >> libz.so.1
>> >> make[3]: *** [Makefile:116:
>> >>
>> /home/ilario/software/lime-sdk/17.01.2/ar71xx/generic/sdk/bin/packages/mips_24kc/limeui/libwebsockets-cyassl_0c7e5a94182b8bf5b5be2fc58141466bf54d5812-1_mips_24kc.ipk]
>> >> Error 1
>> >>
>> >> We're going to deploy more routers (see attached image, work
>> going on).
>> >>
>> >> An interesting thing we noticed:
>> >> using 802.11s for link layer the network doesn't fragment as expected
>> >> when changing the ESSID (using adhoc it was the preferred method for
>> >> splitting networks in layer 2 routing) as the domain now is
>> defined by
>> >> ieee80211s_mesh_id [1]. I suppose we should change this default or
>> >> re-discuss this mechanism for splitting L2 network.
>> >>
>> >> [1]
>> >>
>> https://github.com/libremesh/lime-packages/blob/develop/packages/lime-syste…
>> <https://github.com/libremesh/lime-packages/blob/develop/packages/lime-syste…>
>> >>
>> >>
>> >> On 06/16/2017 05:48 PM, Paul Spooren wrote:
>> >>> HI Ilario, how did you created the image?
>> >>>
>> >>> Cheers,
>> >>> Paul
>> >>>
>> >>> On 16.06.2017 16:59, Ilario Gelmetti wrote:
>> >>>> Hi all!
>> >>>> Here in Hackmeeting-it [1] we reflashed every router in the
>> original
>> >>>> network setup with LibreMesh :D
>> >>>> We used unstable image taken from repo.libremesh.org
>> <http://repo.libremesh.org> using 802.11s and
>> >>>> up to now works perfect with 30 clients :D
>> >>>> Bye!
>> >>>> Ilario
>> >>>>
>> >>>> [1] https://hackmeeting.org/hackit17/
>> <https://hackmeeting.org/hackit17/>
>
>
> _______________________________________________
> lime-users mailing list
> lime-users(a)lists.libremesh.org
> https://lists.libremesh.org/mailman/listinfo/lime-users
--
bruno(a)pobox.com ▀─█▄██▄▀▄
http://brunovianna.net ─█▄██▄▀█▀█▄
skype: randomico▀─█▄██▄▀█▀█▄▌██─█▌█▌
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
Hola! Esta es mi primera participación en la lista. No puedo escribir en
inglés pero si puedo leerlo, al menos los términos informáticos.
Trataré de usar la terminología apropiada, pero si hago mal uso de algún
término les agradezco la corrección, y aprendo un poco más.
Es la primera vez que uso LiMe me falta mucho para aprender de redes.
Estoy tratando de conectar LiMe con la red wifi de mi vecino para salir
a internet desde su conexión. Él no tiene LiMe. En el techo de su casa
pondría un access point HP V-M200 (es lo que único que tengo hasta que
llegue LibreRouter :)
He logrado establecer el enlace de radio entre ellos y obtener
respuestas de pings desde ambos lados. Desde LiMe hacia afuera, solo
puede lograrlo desde Network/Diagnostics... y no tengo internet :-(
En algún momento pude acceder a un servidor web que tengo en una de las
subredes, pero no salir a internet. Creería que el problema es el nuevo
gateway para internet que no se conoce ¿O tendría que definir reglas de
ruteo para salidas a internet?
¿Cómo le cuento a LiMe que la salida a internet no es por la interfaz
WAN del eth1? Quiero que salga por WWAN de Client "wifiVecino"?
¿Qué debo estudiar ahora? =-O
Muchas gracias por la ayuda.
Seba
---
El software de antivirus Avast ha analizado este correo electrónico en busca de virus.
https://www.avast.com/antivirus
i took my day off to test libremesh with 11s.
i could say: 11s works with lede 17.01.2 based cooker-builds ootb. BUT:
i need to trigger the strange networking restart fix as in
https://github.com/libremesh/network-profiles/blob/master/openNET.io/1144-W…
(iirc this is related to the "Internet traffic not going through" thread
on the list).
anybody has any hint how to debug, what is needed to prevent using this
imho dirty fix? i have no idea where this bug comes from. with the
default lime-profile with adhoc-mode everything is fine, as soon as i
use the lime-11s profile i need to trigger a network restart on the
non-gateway nodes to get routing to 0.0.0.0/0 - internal routing inside
10.13.0.0/16 works as intended. the inet4-bmx6-tunnel exists. the nodes
could see each other via batman-adv and bmx6.
for the sake of completeness:
i've built my images with:
adhoc-mode:
./cooker -c ar71xx/generic --profile=tl-wr1043nd-v2 --flavor=lime_default
11s-mode:
./cooker -c ar71xx/generic --profile=tl-wr1043nd-v2
--flavor=lime_default --community=libremesh/11s
greetings from jena/germany,
micha
Hi
I have a strange issue where sometimes, seemingly after a new gateway appears on the network, other routers that were offline during the change, cannot route internet traffic correctly even though BMX tunnels shows everything as being perfect, including the inet4 line with the exit node saying internet.
Steps to reproduce:
1] set up a node with internet access [A]
2] connect client via ethernet to a known to work second [and non-exit] node [B] which is wirelessly meshing with [A]
3] ping internet from client [it works]
4] shut down [A]
5] shut down [B]
6] turn on a new node [C] with the exact same config as [A] and connect it to the same WAN
7] turn [B] back on
Everything in luci will appear perfectly, you’ll be able to ipv6 ping any node, but any internet bound traffic will time out, even from the luci diagnostics page [not a client routes issue].
After rebooting [B], everything works consistently across reboots.
I’ve yet to try with standard 1607, but I’m using an extremely lightly modified config. I’ll do that tomorrow anyway.
Is there a way to restart batman to see if that’s the issue? [can’t find its entry in “startup”] Is there a way to restart some other service to figure out what the issue is? What should I look for in logs?
Is there a general way to force-reset something if a node sees a mesh exit-node but somehow isn’t able to route traffic to it?
Thank you
Nk
Hi,
I have been seeing messages on different topics mentioning the next
release, I have not followed them carefully.
I think I once listened or read the next release won't be compatible
with the current one (maybe because of 802.11s??). Is that correct?
Cheers!
