On 12/15/2017 03:39 PM, Nicolas Pace wrote:
On Tue, 2017-12-12 at 18:55 -0800, Carlito Nueno
I have nodes A, B, C and all are mesh.
Node A is the exit node - connected via ethernet cable on eth0 and
node B and node C are connected A via mesh.
So, when I connected node C via ethernet, does it start using
as backhaul or still keeping mesh.
AFAIK, there is still a bug that makes this not work.
Can't remember about such a bug...
You should not be connecting nodes via cable that can
see each other
via mesh, unless you disable meshing via wireless.
Why, I think it's perfectly ok to do so.
In hackmeeting-it we did that and we observed not a problem:
that is, when
a client connects via wifi to node C, does the traffic
go via option 1 or option 2?
client wifi <--> node C <--> mesh iface <--> node A <--> router
client wifi <--> node C <--> ethernet eth0 <--> router
the ideal would be to aggregate the links,
Aggregate like multipath? I'm not sure there's any wireless community
network doing that.
use the best available, but
as I understand, there is a bug on batman-adv that makes this not work.
Does anyone know more about this? In my opinion should just work fine.
> Is there a way to check/test which interface is
being used when both mesh and Ethernet are connected?
I don't have a device for checking but you can try with:
ip route show
bmx6 -c show=tunnels
> Also, you mention “disable meshing via wireless”,
so you can mesh via Ethernet?
Well, the routing protocols should be already active also on the
ethernet interfaces. You can just connect the routers with a cable.
Just take care of not connecting a LAN port on a LibreMesh router with a
WAN port on another LibreMesh router, you should connect LAN ports to
LAN ports and (sounds strange but should be just ok) WAN ports to WAN ports.