The LibreMesh team is happy to announce a new version of LibreMesh, 2020.1 "ExpansiveEmancipation".
Three years of work, 882 commits, 23 developers, tons of bug fixes and improvements!
This release is compatible with OpenWrt stable 19.07.5 and old-stable 18.06.9.
For the time source-only release so you will need compile it yourself for the devices used by your community using the easy to follow instructions in https://libremesh.org/development.html
## What's in 2020.1 "Expansive Emancipation"
It is imposible to do a meaninful list of all the changes. A non complete list of the most relevant developments:
* LimeApp: an app to for the maintenance and deploy of community networks targeted to non-technical community members. https://github.com/libremesh/lime-app/
* A new community-oriented configuration system that facilitates collective maintenance of configurations.
* shared-state, a shared database for the network.
* first-boot-wizard, an optional helper to deploy and extend the network that it is well integrated with the LimeApp.
* Pirania, an optional boucher and captive portal solution for community networks https://github.com/libremesh/lime-packages/blob/master/packages/pirania/Rea…
* Hundreds of fixes and code improvement.
## Contributors
This release has contributions from communities and individuals from all around the world. Testing, software development, documentation, community building. Thank you all!!
A list of the software developers that contributed to this release was easily gathered from the git history: AngiieOG, Brad, Daniel Golle, FreifunkUFO, German Ferrero, Gioacchino Mazzurco, Gui Iribarren, Ilario Gelmetti, Jess, Luandro, Marcos Gutierrez, Michael Jones, Mike Russell, Nicolás Pace, PatoGit, Pau, Paul Spooren, Pedro Mauro, Santiago Piccinini, Vittorio Cuculo, hiure, radikalbjr, valo.
Best!
SAn
OpenWrt 19.07.5, r11257-5090152ae3
LiMe master development (master rev. d4b8732 20201210_2003)
>From https://libremesh.org/docs/en_connecting_nodes.html
All the nodes are probably in the same collision domain, so you can use
NMAP to discover the nodes in your network and their IPv4s.
nmap -sT -p 80 10.X.Y.0/24 --open
Here: nmap not found
--
Regards
Juergen
Recorded with *Nat.app* <http://Nat.app>
Syslog messages show client has been disconnected for 15 seconds
Sat Dec 12 12:32:32 2020 daemon.notice hostapd: wlan0-apname:
AP-STA-DISCONNECTED 0c:96:e6:4a:b2:8b
Sat Dec 12 12:32:32 2020 daemon.info hostapd: wlan0-apname: STA
0c:96:e6:4a:b2:8b IEEE 802.11: disassociated
Sat Dec 12 12:32:33 2020 daemon.info hostapd: wlan0-apname: STA
0c:96:e6:4a:b2:8b IEEE 802.11: deauthenticated due to inactivity (timer
DEAUTH/REMOVE)
Sat Dec 12 12:32:48 2020 daemon.info hostapd: wlan0-apname: STA
0c:96:e6:4a:b2:8b IEEE 802.11: authenticated
Sat Dec 12 12:32:48 2020 daemon.info hostapd: wlan0-apname: STA
0c:96:e6:4a:b2:8b IEEE 802.11: associated (aid 1)
Sat Dec 12 12:32:48 2020 daemon.notice hostapd: wlan0-apname:
AP-STA-CONNECTED 0c:96:e6:4a:b2:8b
--
Regards
Juergen
Firmware LiMe master development (master rev. d4b8732 20201210_1724) on
19.07.5
thisnode.info does not ask anymore
scan existing network or create new network
BTW scanning never worked here
--
Regards
Juergen
Hi,
I once had a very quick look into this LimeApp or FirstBootWizard, I
cannot remember, I did not played much with it. So let me please be lazy
and ask you directly instead of testing things myself.
I liked this idea of geek-free configuration so that the owner of the
router can configure it themself, buy I wonder if that could leave any
open door for vandalism, because as far as I remember it required to
have a community shared password or something like that?
Or maybe there is any documentation about it?
I get this:
ERROR: please fix package/feeds/libremesh/eupgrade/Makefile - see
logs/package/feeds/libremesh/eupgrade/dump.txt for details
Collecting package info: done
tmp/.config-package.in:72848:error: recursive dependency detected!
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"
tmp/.config-package.in:72848: symbol
PACKAGE_profile-freifunk-80211s-sae-bmx7-batadv depends on
PACKAGE_kmod-cfg80211
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"
tmp/.config-package.in:18758: symbol PACKAGE_kmod-cfg80211 is selected by
PACKAGE_kmod-batman-adv
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"
tmp/.config-package.in:13280: symbol PACKAGE_kmod-batman-adv is selected by
PACKAGE_lime-proto-batadv
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"
tmp/.config-package.in:73299: symbol PACKAGE_lime-proto-batadv is selected
by PACKAGE_profile-freifunk-80211s-sae-bmx7-batadv
tmp/.config-package.in:141221:error: recursive dependency detected!
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"
tmp/.config-package.in:141221: symbol PACKAGE_wpad-mesh-wolfssl is selected
by PACKAGE_wpad-mesh-wolfssl
configuration written to .config
I didn't touch wolfssl at all.
And dump.txt:
Package: eupgrade
Version: x
Depends: +libc +GCC_LIBSSP:libssp +USE_GLIBC:librt +USE_GLIBC:libpthread
Conflicts:
Menu-Depends:
Provides:
Section: lime
Category: LibreMesh
Repository: base
Title:
Maintainer:
Source:
Type: ipkg
Description:
https://github.com/libremesh/lime-packages/
@@
../../libremesh.mk:63: *** Package/eupgrade is missing the TITLE field.
Schluss.
--
Regards
Jürgen
I have a test-network running with a bunch of ac/an Adapters.
I got connections up to 866MBits between the adapters (5Ghz mesh) but even
with this fast connection I only got 40Mbit up/down Speed in direction to
the internet.
Only on the one Adapter connected directly to the Internet i got the full
speed (250/40).
I also played around with distance parameters with no measurable impact.
Are there other possibilities to speed up the mesh?
Thanks in advance,
Andy
