About libremesh used for wired networks instead of wifi networks, it is already
working, probably who focus on the wifi part in their explaining is because the
wifi part is usually more difficult to make works, while cables tends to work
easier, so they probably assumes they just works.
about yggdrasil I stopped reading the page when I saw it is programmed in Go,
which is a programming language which developemnt is almost completely
controlled by google and not really driven by the community.
Cheers
Gio
On Monday, 3 June 2019 22:41:01 CEST fred wrote:
ANyone tried?
https://yggdrasil-network.github.io/
Le 03/06/2019 à 20:59, Patricio Gibbs via lime-users a écrit :
I recently heard a comment something like
"LibreMesh is designed for
wireless mesh networks." But the longest-running community network in
Ecuador using LibreMesh has exactly zero inter-node links via
LibreMesh WiFi. Our network looks like this:
WDR3500 running LibreMesh 17.06 in house A
/\
| UTP/ethernet cable
\/
WDR3500 running LibreMesh 17.06 in house B
/\
| UTP/ethernet cable
\/
5-port switch
/\
| UTP/ethernet cable
\/
WDR3500 running LibreMesh 17.06 in house C
/\
| link between two Ubiquiti LiteBeam M5 running stock firmware
\/
WDR3500 running LibreMesh 17.06 in house D
So... what's going on? Is LibreMesh not tested for wired inter-node
connections? Are hybrid networks that include both wired and wireless
connections not part of the picture? If this is true, then what's the
path from here to the day when we say "LibreMesh is designed for
community mesh networks" regardless of their use of UTP, WiFi, fiber
optic, proprietary WiFi links, or whatever else?
cheers,
~ Patrick
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users