lime

lime-users@lists.libremesh.org

493 discussions

[lime-users] some Android phones not detecting Internet

by Patricio Gibbs

In our network there are three nodes in a chain connected via cable (UTP). Let's call the gateway node A -- it connects via Ubiquiti antennas to a VDSL modem (which should change to a fiber optic connection this month). The nodes were all running LiMe 16.07. Today I flashed node A with LiMe 17.06 (made with Chef, full LibreMesh, tl-wdr3500-v1). Now some Android phones connect to the wifi, detect no Internet, and automatically disconnect, and this happens on all the nodes (B and C are still running 16.07). After trying to connect for a while (maybe 15 or 30 minutes), some of these phones detect Internet and stay connected, while others never detect Internet. Other phones detect Internet immediately and work fine. Computers (GNU/Linux and Windows) detect Internet okay. Looking at LuCI for node A, only itself appears in the Mesh Nodes list, even when people are connected to Internet via node C. Accessing node B and C LuCI works (via casadiego.lan and casafaby.lan), and in their mesh nodes lists, only they appear, not node A. All this didn't happen before upgrading node A. I disabled 5 of the 6 wifi networks on node A because I thought there might be a problem with all the extra wifi networks, but that didn't help. I could upgrade nodes B and C to LiMe 17.06 and see if that makes everything work again, since it seems that there's something incompatible about nodes running different versions of LiMe, but I'd rather just revert to LiMe 16.07 until someone can explain this malfunction and promise that my phone will detect the Internet connection if I upgrade all nodes. However, I can't find the .bin files to flash node A, and the backup I make of node B isn't a .bin file. If I could find those old files, I would also happily test 17.06 on all the nodes, but I can't find any .bin files of LiME 16.07. I could also try modante's solution to a different problem, "manually running the script /etc/watchping/wan-ok.d/bmx6-gw", but it seems different than this problem. ~ Pato

6 years, 11 months

[lime-users] How do I change the IPV6 DNS server announced to IPV6 clients?

by David Medland-Slater

Can anyone point me at how to change the config of libremesh so that an IPV6 client doesn't get the DNS server as the IP address of the libremesh router itself? I can see how to do this for IPV4 in the DHCP server config just fine and that works by using an option 6 and the list of DNS servers I want to use, but doing this for IPV6 has left me stumped. I'm using the 17.06 generic image with no mods. Thanks in advance Dave

6 years, 11 months

[lime-users] Issues with inet4 gateway tunnel announcement

by modante＠disroot.org

Hi Guys. I am having connectivity issues in the mesh network we are running in the neighbor in order to share internet. After 2 days trying to find the issues, the resume is that the announcing of the inet 4 gateway tunnels suddenly stops and doesn't returns but manually running the script /etc/watchping/wan-ok.d/bmx6-gw that instantaneously returns internet connectivity in all the nodes of the mesh. I suspect from whatchping but I have no enough skills to resolve it by myself. I started to report the issue on git but somebody said that would be better to report it here. I am not sure if it worths to repeat all here or only announce it. This is the issue: https://github.com/libremesh/lime-packages/issues/346 (https://github.com/libremesh/lime-packages/issues/346) Thank you very much and regards :-)

6 years, 12 months

[lime-users] Saludos

by Ruben Valiente Farias

Buenas noches, soy nuevo acá y quisiera pedir ayuda para montar una pequeña red mesh acá en Nicaragua....SaludosRubén V.

7 years

[lime-users] How to add libremesh repo to existing openwrt router?

by Kevin Steen

Please can someone tell me how to add the LibreMesh repo for opkg to an existing OpenWrt router? I've tried adding the lines to /etc/opkg/customfeeds.conf, but when I run opkg update the signatures fail: ------ root@LEDE:/etc# opkg update Downloading http://repo.libremesh.org/current/packages/mips_24kc/libremesh/Packages.gz Updated list of available packages in /var/opkg-lists/libremesh Downloading http://repo.libremesh.org/current/packages/mips_24kc/libremesh/Packages.sig Signature check failed. Remove wrong Signature file. ------ I think I'm missing LibreMesh keys from /etc/opkg/keys, but I can't seem to find them anywhere. I had to build a very basic firmware image using Chef for the TP-Link MR3020, so that I could use 'extroot', which is why I think I don't have any LibreMesh keys on my router? Many thanks -Kevin

7 years

[lime-users] Fwd: Mesh is in the air <3 in Berlin in May

by Ilario Gelmetti

Wireless Battle Mesh v11 + Wireless Community Weekend 2018 -------- Forwarded Message -------- Subject: [CNSIG-Council] Invitation - Mesh is in the air <3 in Berlin in May Date: Tue, 3 Apr 2018 18:32:28 +0200 From: Monic Meisel <monic(a)monic.de> Reply-To: CNSIG Council <council(a)lists.cnsig.info> To: CNSIG Council <council(a)lists.cnsig.info> Hello, thanks for the warm welcome :) I would like to start with an invitation to all of you: Meet with us at our next community event: Mesh is in the air <3 The Wireless Battle Mesh v11 (#WBMv11) and the Wireless Community Weekend 2018 (#FFWCW18) will be meshed up and co-located in Berlin from May 07 to May 13, 2018. Since it is the 15th anniversary of the WCW, friends and fellows from across the globe celebrate together wireless mesh network technologies and ideas of community networking. -> Please check here for more info and register yourself, if you will attend: https://www.wireless-meshup.org And I would like to continue with a call for endorsement until April 7th and sessions until 15th: - If you like to endorse the event, please check our template and spread the announcement through your channels: https://www.wireless-meshup.org/doku.php/endorsements - I would love to have one representative from each working group onboard to tell the freifunk community first hand, what it is about and how to contribute. — Panos will be there and introduce "Social impact“ — so at least "Policy and regulation“ and „Technical“ is missing ;) — Is anyone able to tell something about or start "Training, capacity building and knowledge sharing" - The schedule starts growing, please have a look: https://www.wireless-meshup.org/doku.php/schedule Thursday or Saturday, would be great to offer the CNSIG Introduction, and if you like, run a workshop, brainstorming or other session to attract attendees to the WGs - It would be great, if you would introduce your community or project or technical issue to our audience to connect with Freifunk and Battlemesh Community. - Also I am searching for one, who can tell the community about this net commons work stream, since Jürgen will unfortunately not be available .. who can help out? https://www.youtube.com/playlist?list=PLKXvzLAP_vSYkQpXmheK99AZkAtAoTaUv !! We do provide travel funding, please check this page, send us a mobile phone video (or short description, if this is easier) since the application period is running out soon: https://www.wireless-meshup.org/doku.php/start We would appreciate to welcome you in Berlin! Best regards Monic

7 years

[lime-users] Cross-compiling Libremesh for Zynq board

by Musab Isah

Dear Pau, all I followed the directions in your earlier reply (attached) to the email I sent to you directly. I cross-compiled libremesh for zynq board and got the following files in the output folder: drwxrwxr-x 2 meshnet meshnet 4096 Apr 2 14:11 ./ drwxrwxr-x 3 meshnet meshnet 4096 Apr 2 14:11 ../ -rw-rw-r-- 1 meshnet meshnet 4760 Apr 2 14:11 lede-17.01.4-lime-default-zynq-device-zedboard.manifest -rw-rw-r-- 1 meshnet meshnet 3593943 Apr 2 14:11 lede-17.01.4-lime-default-zynq-device-zedboard-rootfs.tar.gz -rw-rw-r-- 1 meshnet meshnet 6972488 Apr 2 14:11 lede-17.01.4-lime-default-zynq-zc702-fit.itb -rw-rw-r-- 1 meshnet meshnet 3612119 Apr 2 14:11 lede-17.01.4-lime-default-zynq-zc702-uramdisk.image.gz -rw-rw-r-- 1 meshnet meshnet 6967804 Apr 2 14:11 lede-17.01.4-lime-default-zynq-zed-fit.itb -rw-rw-r-- 1 meshnet meshnet 3612119 Apr 2 14:11 lede-17.01.4-lime-default-zynq-zed-uramdisk.image.gz -rw-rw-r-- 1 meshnet meshnet 6967660 Apr 2 14:11 lede-17.01.4-lime-default-zynq-zybo-fit.itb -rw-rw-r-- 1 meshnet meshnet 3612119 Apr 2 14:11 lede-17.01.4-lime-default-zynq-zybo-uramdisk.image.gz -rw-rw-r-- 1 meshnet meshnet 939 Apr 2 14:11 sha256sums But based on the requirements for booting a zedboard here http://www.wiki.xilinx.com/OpenWrt+running+on+ZC702, there are many files that are missing as you can see from the list. Using the files produced by lime-sdk alone could't get zedboard to boot. So I built an openwrt image for Zedboard (I am using this board https://reference.digilentinc.com/reference/programmable-logic/zedboard/sta…), which generated some of the files that are missing, as listed below. -rw-r--r-- 1 meshnet meshnet 66228 Apr 2 16:32 boot.bin -rwxr-xr-x 1 meshnet meshnet 2998844 Apr 2 16:32 u-boot* -rw-r--r-- 1 meshnet meshnet 8014 Apr 2 16:32 u-boot.dtb -rw-r--r-- 1 meshnet meshnet 427722 Apr 2 16:32 u-boot-dtb.bin -rw-r--r-- 1 meshnet meshnet 427786 Apr 2 16:32 u-boot-dtb.img -rwxr-xr-x 1 meshnet meshnet 1056160 Apr 2 16:32 u-boot-spl* -rw-r--r-- 1 meshnet meshnet 63988 Apr 2 16:32 u-boot-spl-dtb.bin I copied these missing files together with the files produced via lime-sdk to my sdcard and tried to boot the board but the terminal keeps reading **Unable to read file fit.itb **. When building the openwrt image for the board, I also generated the sdk and the imagebuilder for it. I tried to make a custom build of image with the sdk and the ib but get the following error: tmp/.config-package.in:3740:error: recursive dependency detected! For a resolution refer to Documentation/kbuild/kconfig-language.txt subsection "Kconfig recursive dependency limitations" tmp/.config-package.in:3740: symbol PACKAGE_lime-basic-uing depends on PACKAGE_kmod-ebtables For a resolution refer to Documentation/kbuild/kconfig-language.txt subsection "Kconfig recursive dependency limitations" Segmentation fault (core dumped) /home/meshnet/lime-sdk/openwrt/zynq/generic/sdk/include/toplevel.mk:136: recipe for target 'menuconfig' failed make[2]: *** [menuconfig] Error 139 make[2]: Leaving directory '/home/meshnet/lime-sdk/openwrt/zynq/generic/sdk' /home/meshnet/lime-sdk/openwrt/zynq/generic/sdk/include/toplevel.mk:97: recipe for target '.config' failed make[1]: *** [.config] Error 2 make[1]: Leaving directory '/home/meshnet/lime-sdk/openwrt/zynq/generic/sdk' /home/meshnet/lime-sdk/openwrt/zynq/generic/sdk/include/toplevel.mk:209: recipe for target 'world' failed make: *** [world] Error 2 make: Leaving directory '/home/meshnet/lime-sdk/openwrt/zynq/generic/sdk' -> Error compiling SDK And when I tried to cook the image without building using custom sdk and ib, I got the following: Collected errors: * opkg_install_cmd: Cannot install package lime-full. * opkg_install_cmd: Cannot install package lime-app. Makefile:134: recipe for target 'package_install' failed make[2]: *** [package_install] Error 255 Makefile:100: recipe for target '_call_image' failed make[1]: *** [_call_image] Error 2 Makefile:175: recipe for target 'image' failed make: *** [image] Error 2 make: Leaving directory '/home/meshnet/lime-sdk/openwrt/zynq/generic/ib' Could you please advise? Many thanks for your help. Musab

7 years

[lime-users] 3g/4g USB modem plugged into LibreMesh router

by Patricio Gibbs

Has anyone used a 3g/4g USB modem plugged into a LibreMesh-ed router as their Internet connection? We want to know if it works, and how you configured it. In central Ecuador, we want to plug a USB cellular modem into a router running LibreMesh, and use that as our Internet connection. It's supposed to be a short-term solution while we work on getting a wired connection, and given the conditions, it may turn out to be a decent backup connection for a while. However, we'll calculate the long-term costs compared to a wired connection, so the community can make an informed decision. ~ Patrick

7 years

[lime-users] DIY signal boosters

by amuza

Hi, What is your experience with Do-It-Yourself Wi-Fi signal boosters? Anyone tried the one on the attachment? Cheers

7 years

[lime-users] Gateways fail to be offered on latest chef builds

by Paul Harmor

After weeks of trial and error and troubleshooting on several different Chef builds (1x ar71xx/wndr3700v2, 3x x86 of all different hardware), default LiMe 802.11s profile, I've come to the conclusion that watchping or some other link in the chain is failing to offer the gateway. At any time, if any node loses WAN uplink, it and it's clients will sit without internet for hours, while still communicating with all other nodes and machines on the network. After some chat in the dev channel, the fact that I was using USB WiFi devices as WAN interfaces, set up with the LEDE/OPENWRT default WWAN iface name, became suspect as the cause. Unfortunately however, neither changing the reference in the watchping settings in /etc/config/system, nor changing WWAN to WAN as the actual interface used made any difference. The nodes CAN communicate (thus not the usual "can't ping" bug), Uplink is recognized as lost by watchping, but the node with one does not ever offer it up. Once again, this is with the default 802.11s profile, meaning BMX6. I have not yet tried BMX7, as I'm not sure how to migrate from one to the other in place.

7 years, 1 month

← Newer
1
...
22
23
24
25
26
27
28
...
50
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

lime