Hi all, 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 ethernet as backhaul or still keeping mesh.

that is, when a client connects via wifi to node C, does the traffic go via option 1 or option 2? option 1: client wifi <--> node C <--> mesh iface <--> node A <--> router option 2: client wifi <--> node C <--> ethernet eth0 <--> router

Is there a way to check/test which interface is being used when both mesh and Ethernet are connected?

Also, you mention “disable meshing via wireless”, so you can mesh via Ethernet?

On Friday, December 15, 2017, Nicolas Pace &lt;nico(a)libre.ws&gt; wrote: > On Tue, 2017-12-12 at 18:55 -0800, Carlito Nueno wrote: > > Hi all, > > > > 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 > > ethernet > > as backhaul or still keeping mesh. > > AFAIK, there is still a bug that makes this not work. > You should not be connecting nodes via cable that can see each > other > via mesh, unless you disable meshing via wireless. > > > that is, when a client connects via wifi to node C, does the > traffic > > go via option 1 or option 2? > > > > option 1: > > client wifi <--> node C <--> mesh iface <--> node A <--> router > > > > option 2: > > client wifi <--> node C <--> ethernet eth0 <--> router > > the ideal would be to aggregate the links, use the best available, > but > as I understand, there is a bug on batman-adv that makes this not > work. >