Ilario Gelmetti

I believe that adding some documentation about how to configure the routers in this scenario can mitigate this issue, do you agree? So, for the upcoming release we should either...

Also, this interface-specific configuration should be exposed via lime-app, as it is veeery common for users to connect two LibreMesh devices via ethernet (I believe). Opinions? @selankon @javierbrk @G10h4ck

The issue #1008 is like a child of this one. I hope that when this one will be fixed, also #1008 will really be fixed.

The default configuration aims to support both LibreMesh_node---Client and LibreMesh_node---LibreMesh_node ethernet connections. While this maybe worked for both scenarios in the past, currently it works only for the first case,...

In case we should remove also Babeld, we can add the same check here: https://github.com/libremesh/lime-packages/blob/c3ef5a80929dee895be3661a60e8b700324e4e5b/packages/lime-proto-babeld/files/usr/lib/lua/lime/proto/babeld.lua#L95-L97

@pony1k amazing research!! The only thing I can say (not very useful though) is that we can already use VLAN 802.1q just specifying it in the /etc/config/lime-node with something like:...

@javierbrk @G10h4ck opinions?

The error messages look like this: ``` [ 121.472686] batman_adv: bat0: Possible loop on VLAN -1 detected which can't be handled by BLA - please check your network setup! [...

The error messages are the same as the ones observed in https://github.com/libremesh/lime-packages/issues/189, but there there was (also?) another problem that has been solved in https://github.com/libremesh/lime-packages/pull/726

More info in this email: https://lists.autistici.org/message/20240714.140352.58fe57b2.en.html Once detected, a possible solution would be to add a huge warning in lime-config output suggesting how to fix this manually (the detection script...