Hi,
A node is connected to Internet gateway A, but it also has access to
Internet gateway B. If gateway A fails, how long does it take to start
using gateway B?
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
Hey,
I'm trying to compile again LiMe based on OpenWRT 19.07, but now I get
many errors.
When I was in the configuration menu (make menuconfig) I could not find
LiME packages, so I decided to start compiling again but now watching
carefully to find errors.
Please see below the first one I got:
amuza@18.04:~/git$ sudo apt install --no-install-recommends git
ca-certificates subversion wget make gcc g++ libncurses5-dev gawk unzip
file patch python3-distutils python3-minimal python2-minimal
libpython2-stdlib
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package python2-minimal
E: Unable to locate package libpython2-stdlib
I tried to get those two files for Ubuntu 18.04, but could not make it,
I installed some similar files, but it keeps complaining.
Please find attached a text file with all the errors I got after this one.
Thank you very much.
I had less time to test, so this comes really late - The Problem exists
since 2 weeks:
I use an ex6150v2 to connect the Tesmesh to the Internet (1GBit ETH-Port
manually assigned as WAN): I used openwrt 19.07.4 with libremesh 20.09 and
got no IP V4 address. (And no: the babeld is running ;-) It is another
Problem than in snapshot - which is solved atm).
The connected Meshnotes give the Mobile Device an ip v4, so there it is
working - but not connected to the "Gateway" (Neither in pa nor in apname
Mode). So I checked and reverted the WAN Port to an LAN Port - the
connected PC does also get any ip v4 address.
I compiled new with 19.07 (as newly advised by Ilario) and libremesh (not
branched to 20.09)
Still the same behavior.
Any thoughts on this?
Regards,
Andy
Going back to 19.07.3 because of ethernet time out errors in ramips I got
this:
WARNING: Makefile 'package/utils/busybox/Makefile' has a dependency on
'libpam', which does not exist
WARNING: Makefile 'package/utils/busybox/Makefile' has a build dependency
on 'libpam', which does not exist
WARNING: Makefile 'package/network/utils/curl/Makefile' has a dependency on
'libgnutls', which does not exist
WARNING: Makefile 'package/network/utils/curl/Makefile' has a dependency on
'libopenldap', which does not exist
WARNING: Makefile 'package/network/utils/curl/Makefile' has a dependency on
'libidn2', which does not exist
WARNING: Makefile 'package/network/utils/curl/Makefile' has a dependency on
'libssh2', which does not exist
WARNING: Makefile 'package/network/utils/iproute2/Makefile' has a
dependency on 'libcap', which does not exist
WARNING: Makefile 'package/network/utils/iproute2/Makefile' has a
dependency on 'libcap', which does not exist
WARNING: Makefile 'package/network/utils/iproute2/Makefile' has a
dependency on 'libcap', which does not exist
WARNING: Makefile 'package/network/utils/iproute2/Makefile' has a
dependency on 'libcap', which does not exist
WARNING: Makefile 'package/network/utils/iproute2/Makefile' has a
dependency on 'libcap', which does not exist
WARNING: Makefile 'package/network/utils/iproute2/Makefile' has a
dependency on 'libcap', which does not exist
WARNING: Makefile 'package/network/utils/iproute2/Makefile' has a
dependency on 'libcap', which does not exist
WARNING: Makefile 'package/network/utils/iproute2/Makefile' has a
dependency on 'libcap', which does not exist
WARNING: Makefile 'package/boot/kexec-tools/Makefile' has a dependency on
'liblzma', which does not exist
WARNING: Makefile 'package/network/services/lldpd/Makefile' has a
dependency on 'libnetsnmp', which does not exist
WARNING: Makefile 'package/network/utils/nftables/Makefile' has a
dependency on 'jansson', which does not exist
--
Regards
Jürgen