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
Great news:
SAn TAGGED A RELEASE CANDIDATE FOR THE LIBREMESH 20.09 RELEASE!!
Even if the LibreMesh development never stopped, it was since the 17.06
"Dayboot Rely" release that we didn't have an _official_ release.
The goal is to have the **final release at the beginning of November**.
This means that the release candidate needs testing, bug fixing and
loads of community love before the end of October, so that we can have
an amazing release that can actually ease the creation of community
networks everywhere :)
We can coordinate the efforts on this mailing list and on the
IRC/Element chatroom (Element is the new name of Riot chat):
https://libremesh.org/communication.html
Seems that the next release will be (at least initially) source-only,
which means that you will have to compile it yourself on top of OpenWrt
18.06.8 or 19.07.4. Right now there's no way to download the
pre-compiled binary, but I hope this will be available at some point.
In order to compile the release candidate follow the instructions from
the Development page:
https://libremesh.org/development.html
As you can see in the compiling instructions, both OpenWrt 18.06.8 or
19.07.4 can be used as a base, but I think we should have more testing
on the newest 19.07.4 (until now the testing has been focussed mostly on
18.06.8).
There's no need to select the release candidate branch for the
compilation, seems that the master branch will be used also for the
testing and the relevant commits will be cherry-picked in November (SAn,
please correct if I'm wrong).
You can see the known issues on the tickets list:
https://github.com/libremesh/lime-packages/issues
And if you want to take care of an issue (thanks!!!), please have a look
at these lists where you can find some indication of the priority:
https://github.com/orgs/libremesh/projects/2
A last thing:
do we need a codename for the release or "20.09" is enough?
Propose your favourite name, starting with the "E" letter if possible,
on the chatroom and then we'll organise a poll :)
Thanks!!!
Ilario
--
Ilario
iochesonome(a)gmail.com
ilario(a)sindominio.net
On Dec 2, 2020 01:03, amuza <amuza(a)riseup.net> wrote:
>
> Hi again,
>
> My LiMe network uses 10.5.0.0/16.
>
> Among the many addresses I see when I run `ip addr` I find the following:
>
> 12: eth0.2@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
> noqueue state UP group default qlen 1000
> link/ether c0:4a:00:7a:b7:ed brd ff:ff:ff:ff:ff:ff
> inet 192.168.0.31/24 brd 192.168.0.255 scope global eth0.2
> valid_lft forever preferred_lft forever
> inet6 fe80::c24a:ff:fe7a:b7ed/64 scope link
> valid_lft forever preferred_lft forever
>
> Why do I have an IP address belonging to the 192.168.0.0/24 network?
> What is it for?
Hi Amuza!
That looks like the WAN port of a router connected to a non-LibreMesh router for getting internet access. If this is correct then that address is for reaching the ISP gateway (your modem) and reaching the internet. And your LibreMesh node received that IP from the DHCP server on the ISP modem/router.
Ciao!
Hi again,
My LiMe network uses 10.5.0.0/16.
Among the many addresses I see when I run `ip addr` I find the following:
12: eth0.2@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
noqueue state UP group default qlen 1000
link/ether c0:4a:00:7a:b7:ed brd ff:ff:ff:ff:ff:ff
inet 192.168.0.31/24 brd 192.168.0.255 scope global eth0.2
valid_lft forever preferred_lft forever
inet6 fe80::c24a:ff:fe7a:b7ed/64 scope link
valid_lft forever preferred_lft forever
Why do I have an IP address belonging to the 192.168.0.0/24 network?
What is it for?
