lime June 2019

lime-users@lists.libremesh.org

12 participants
13 discussions

by Kleper

Hello, I write to ask in the list that brand and references of equipment designed to work outdoors can recommend me different from the brand Ubiquiti because for a couple of months we have been having trouble changing the firmware to this brand computers that are supposedly compatible but come with a new firmware version and do not allow the installation of libreMesh. I hope you can give us more information about it. Thank you. Fernando Castro T

4 years, 7 months

[lime-users] LuCI and lime-app

by Patricio Gibbs

In my experience LuCI is very useful for editing configuration and monitoring the network. LuCI offers an intermediate step between the simplicity of lime-app and the complexity of SSH command line configuration. Given this usefulness and the alpha status of lime-app, I will likely install LuCI on devices for the moment, and maybe uninstall lime-app to save space and RAM until lime-app reaches release status. Would this interfere with the functioning of LibreMesh? For example, with LuCI I can: - monitor network traffic quantity and connections - set static routes for local services - configure WWAN (internet connection via wifi) - set a static address for WAN client (this was necessary in one of our networks) - see what devices are connected - look at logs - change wifi SSID, hide SSID, change wifi password, create MAC-based access control list - install and remove packages Without LuCI, I either have to: 1) give up on these things, 2) configure them at the moment of compiling firmware and reflash the device, or 3) learn how to do these things via SSH (and forget about having pretty charts on the command line). cheers, Patrick

4 years, 9 months

[lime-users] Backup uplink for a Libremesh router?

by Martin Buhr

Hi, I've got a USB 4G dongle and have successfully hooked it up to a router running libremesh using the RNDIS documentation from the OpenWRT documentation site. However once that router joins a mesh, the IPv4 address data vanishes (it is connected via LAN). However, I don;t actually need this node to be connected, I actually just need to have the main router that has a direct WAN connection to the internet, to *also* have a USB dongle, but use it as a fallback or failover should the main WAN connection go down. I've tinkered with Mwan3, but it just broke my internet all together (I think because it uses static routes). I was wondering if something like this was even possible or if anyone's done something similar with a secondary uplink? Thanks again! Martin

4 years, 10 months

[lime-users] Archer C50 adventures

by bruno vianna

Hello meshies I know everybody is having fun at Battle Mesh, but if someone could take a look at this I' d really appreciate. I really have my eyes on the C50, as it seems to be the cheapest dual-band on the market now. I can get on in Brazil for less than 40 USD! Last week I bought one which I later found out to be an unsupported V2. But now I got a V1, and it almost works. If it works, I'll the buy about 10 for an installation in two weeks. The problem seems to be with 802.11. The 2.4Ghz radio does not work in ad-hoc mode - although the 5Ghz radio does. Then I don't know if it's related, but when it meshes with a WDR3500, the Internet is painfully slow, with some ping times about 1000-2000 milliseconds. Pinging from the LiMe gateway at the same time gives me a steady 57ms. Perhaps a different driver should be used? Attached is a file with information gathered from the router. A few other oddities (not as important as the issue above): - Could not flash from stock directly with the compiled LiMe. I had to first use this openwrt [1], then LiMe - When I flash from the firmware above with the LiMe I compiled or the download Lede, I get the message: " It appears that you try to flash an image that does not fit into the flash memory, please verify the image file! Size: 7.63 MB (7.62 MB available)" It works fine, tough. - The firmware I cooked with my community settings (using cooker) won't go through to the Internet, and gives this ESSID instead of my community's:{{NETWORK_NAME}} (although it meshes with the LiMe gateway) - The firmware I cooked without community settings connects to the Internet through the LiMe gateway with the sluggish times above. Thanks! [1] http://dl.eko.one.pl/luci/chaos_calmer/ramips/luci-15.05-ramips-mt7620-Arch… -- bruno(a)pobox.com ▀─█▄██▄▀▄ http://brunovianna.net ─█▄██▄▀█▀█▄ skype: randomico▀─█▄██▄▀█▀█▄▌██─█▌█▌

4 years, 10 months

[lime-users] Control which mesh nodes can connect

by Martin Buhr

Hi, I love this project and have already set up a local mesh with a few routers. My concern is that I want to be able to control who adds nodes to the mesh, from what I can tell, just having a flashed router set up with the correct Mesh ID adds it to the routing table, which is a worry if you want a more controlled roll-out, i.e. how do you stop a malicious actor adding a mesh router and just sniffing all the packets (assuming nobody uses VPN or TLS of course, it's hypothetical)? I tried to set up an encrypted mesh with 802.11s but the mesh netowrks vanished after adding he packages and configuration change, I assume because of the two-rdio issue described elsewhere. I was wondering if something simpler, like a MAC whitelist or a node IP whitelist is possible to simply make the network growth a bit more manageable? I understand this goes against the "Libre" principle, and may not be viable with a distributed network, but given I do not have the netowrk skill to figure this out on my lonesome I thought I'd ask. Cheers, Martin

4 years, 10 months

[lime-users] Mesh encryption on 4Mb routers

by Leonardo F. Cardoso

Hello, all. This is my first post to this list. Congratulations for the great project. Sorry for my English. My use case is home meshing to have a self-healing, multi router home networking, like "google mesh" with (maybe) cheap 4Mb flash routers like WR841N / WR941N from TP-Link. I've used latest binaries from website and binaries from "chef" (aparcar / no LUCI) but mesh encryption is not working. This is discussed in https://github.com/libremesh/lime-packages/issues/208 and looks like I need a way to build the firmware with "wpad-mesh" package. When I force this package on "chef", the build works, but it can't create the "sysupgrade" image to flash. I think this is due to resulting size of firmware. Is there a way to produce a functional build with "wpad-mesh" so I will be able to use mesh encryption? Web interface is not a problem. Thanks in advance Leonardo ----------------------------------------- Leonardo F. Cardoso leonardo.f.cardoso(a)gmail.com -----------------------------------------

4 years, 10 months

[lime-users] Chef

by Patricio Gibbs

If chef is currently not working (not creating functional firmware) and not tracking current development of LibreMesh, and therefore isn't the recommend way to create firmware.... how about we put an announcement on chef.libremesh.org and betachef.libremesh.org explaining this? And maybe take chef offline until it works as intended? I think the current situation is causing confusion.

4 years, 10 months

[lime-users] Protocols for longer distance links

by Patricio Gibbs

I've heard that the usual 802.11 WiFi standards were designed for household links, maybe up to a kilometer? And therefore longer distance links tend to use other protocols, with TDMA or other methods. So, if we're going to set up 5km links, 10km links, 20km links, 40km links... at what point does it make sense to stop using standard WiFi? For example, if we set up an 8km link with a MikroTik LHG5 on each end, or a TP-Link CPE610 on each end, will the link quality be the same with stock firmware as with LibreMesh? Up to what distance is this true? cheers, Patrick

4 years, 10 months

[lime-users] [LibreMESH] Actualizar OpenWRT

by Fernando Castro

Hola, Resulta que tengo unos equipos nuevos para NuestraRED.org pero no estan soportados en la versión actual de LibreMESH que viene con lede 17, quisiera saber si alguien puede ayudarme a crear un firmware con la ultima versión de OpenWRT para dar soporte a estos equipos nuevos o si hay alguna forma de instalar los paquetes de LibreMESH en OpenWRT 18 para conectarlos a la RedMesh que ya tengo funcionando. Los equipos que tengo son los siguientes: https://openwrt.org/toh/hwdata/tp-link/tp-link_cpe210_v3 Intente crear los firmware por el CHEF pero los archivos que se generan no parecen quedar bien configurados por que cuando instalo estos firmwares en varios routers no logran la conexión MESH entre ellos. Tambien si alguien puede darme alguna guia para dar soporte a este equipo en la versión actual de LibreMesh seria de mucha ayuda. Gracias.

4 years, 10 months

[lime-users] documentation of how works lepzig mesh (was Control which mesh nodes can connect)

by guifipedro

Hi, [ cc to list as thinking it is interesting for you too ] > We are using SAE with a pre-shared-key as well as BMX7 with signed > routing information to implement granular access control to our > local mesh and gateway here in Leipzig Daniel, Paul, are you coming to battlemesh.org v12 in Paris? I confirm that will be there. Would be nice place to clarify how your network works. Questions & Requests 1. configuration example / backup : For me it is enough a /etc/config (backup) of a nanostation for example. Or the libremesh profile you are using (then I would run that profile in a nanostation to see that config). Are you running just bmx7, or you have another layer with batman-advance? 1.1 Of course, if you have more documentation related to your network would be nice 2. in another reply Daniel you said that with 4 MB of flash is impossible to setup all this stack. Confirm. (In my case I would not need luci) - it's the case for some alfa network antennas 3. I have so much devices with 32 MB of RAM, it runs OK with your setup? [1] Thank you very much, Pedro [1] For example, my network what I would like to migrate to what you did is (more info http://dsg.ac.upc.edu/qmpsa/index.php): ALFA Network N2/N5 ALFA Network N2/N5 AMD GX-412TC SOC AMD GX-412TC SOC TP-LINK TL-WDR3600/4300/4310 Ubiquiti Bullet M Ubiquiti Loco M XW Ubiquiti Nanostation M Ubiquiti Nanostation M Ubiquiti Nanostation M Ubiquiti Nanostation M Ubiquiti Nanostation M Ubiquiti Nanostation M Ubiquiti Nanostation M Ubiquiti Nanostation M Ubiquiti Nanostation M Ubiquiti Nanostation M Ubiquiti Nanostation M Ubiquiti Nanostation M Ubiquiti Nanostation M Ubiquiti Nanostation M Ubiquiti Nanostation M Ubiquiti Nanostation M Ubiquiti Nanostation M Ubiquiti Nanostation M XW Ubiquiti Nanostation M XW Ubiquiti Nanostation M XW Ubiquiti Nanostation M XW Ubiquiti Nanostation M XW Ubiquiti Nanostation M XW Ubiquiti Nanostation M XW Ubiquiti Nanostation M XW Ubiquiti Rocket M XW Ubiquiti Rocket M notes: when there is no XW means XM, for example Ubiquiti Nanostation M => XM series my conclusion is that my network right now is so legacy to migrate? (depends a lot on response 3 / 32 MB RAM issue)

4 years, 10 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

lime June 2019