lime April 2018

lime-users@lists.libremesh.org

10 participants
8 discussions

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▀─█▄██▄▀█▀█▄▌██─█▌█▌

5 years, 5 months

[lime-users] Current options of a captive portal for LiMe

by Amuza

Hello, Here we are considering again the captive portal thing. It would be a welcome page with some community news, not real authentication. I guess we would like a system where MAC addresses of users who just clicked an "Ok" button of the splash page would be validated for a month. So they would have to go through this News page once a month. I've seen Nodogsplash seems to be maintained again, so I can try to make it work for LiMe. But first I wanted to ask about Pitbull, as I think that was something similar but specially made for LiMe. What is the status of Pitbull? Would it work for the described need? Thank you!

6 years, 4 months

[lime-users] Little steps in the good direction

by Amuza

Hey sisters, Let me share some good news for community networks -and bad ones for ISPs: 0.- Bitmessage has been working on LAN peer auto-discovery. It is already in v0.6 branch, we tested it and it works. 1.- Retroshare will finally have asynchronous messaging working (Retroshare already has LAN peer auto-discovery). 2.- Impressive ZeroNet is aware of the importance of LAN peer auto-discovery and they are going to add this feature.

6 years, 4 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, 8 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.

6 years, 8 months

[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

6 years, 8 months

[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

6 years, 8 months

[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

6 years, 8 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

lime April 2018