Ok sorry so just to confirm, the options then are 1] WAN to WAN and 2] LAN to LAN, and both routers can also have traditional LAN clients on the remaining 3 eth1 ports that receive DHCP as usual without any interference? At this point my setup would be the one you can find attached. If you confirm it works, I’ll test it out tonight. Thank you so much.

On May 10, 2017, 3:37 PM +0200, Nicolas Pace <nico@libre.ws>, wrote:

On Wed, 2017-05-10 at 15:34 +0200, Nk via lime-users wrote:

AHAHAHAH epic.

Thanks Ilario, sorry to bother. My tests were first router’s LAN to
second router’s WAN, and that wasn’t working. Are you saying they
should be connected LAN to LAN [as an alternative to WAN to WAN which
we know works perfectly]? Wouldn’t that cause a DHCP conflict?

Not at all. That is the default behaviour of LibreMesh (crazy, right?
:) ).

Thank you.

Nk

On May 10, 2017, 3:33 PM +0200, Ilario Gelmetti <iochesonome@gmail.co
m>, wrote:

On 05/10/2017 02:20 PM, Nikksno via lime-users wrote:

If I use the eth1 of the first router to mesh with other routers
as
you're suggesting, the problem is that the meshing doesn't seem
to
happen correctly, as bmx6 shows the second router's route as
being eth1,
but batman shows all routes to other nodes being over wlan mesh,
even to
the second router.

 
It's not lan, it's not wan...
It's BATWAN nananananananananananananananana batwaaaaaannn

No, seriously, I expected batman was present on ethernet LAN
interfaces...
They're also included in br-lan which is included in bat0, no?

Can you post these?
# brctl show
# batctl if

I agree with nicopace, lan to lan should work.
@devs pls? Are ethernet ports with LAN proto not used by batman-
adv?
_______________________________________________
lime-users mailing list
lime-users@lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users

_______________________________________________
lime-users mailing list
lime-users@lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users