-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Detect LAN-switch-LAN connection situations #1118
Comments
The error messages look like this:
and the effect is an unstable network. |
More info in this email: 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 would run during lime-config execution). And the same warning should appear in lime-app with some buttons for fixing. |
@pony1k did not observe any issue connecting two DSA-supported LibreMesh routers to a dumb switch. And the batman-adv on the two routers were also detecting each other via the cable (that did not happen in my tests). |
The switch between nodes should not make the situation worse than #1121, so we can continue the discussion there. |
Within the cable purpose autodetection GSoC project by Nemael, we have the option to configure an interface once we detect a specific situation.
When 2 LibreMesh routers are connected to a switch (from another router or a third LibreMesh router) batman-adv has problems and specific configuration has to be applied to those LAN ports in order for the network to work, like this.
The question here is how to detect if a LAN port is connected to a network with LibreMesh data on it (either directly to a LibreMesh node or through a switch).
The text was updated successfully, but these errors were encountered: