Skip to content
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

mwan3: mwan3_set_connected not updated when new routes are added #13200

Closed
aaronjg opened this issue Aug 24, 2020 · 1 comment · Fixed by #13169
Closed

mwan3: mwan3_set_connected not updated when new routes are added #13200

aaronjg opened this issue Aug 24, 2020 · 1 comment · Fixed by #13169
Assignees

Comments

@aaronjg
Copy link
Contributor

aaronjg commented Aug 24, 2020

Maintainer: @feckert
Environment: 19.07.3, mwan3 2.9.0 and before

Description:
mwan3 has special handling for addresses that have explicit routes in the main routing table. For these routes, the default route is used, and when multiple routes are available, the interface is chosen by the kernel based on the metric in the main routing table.

It handles this by using ipsets called mwan3_connected_v{4|6}. However, this is never updated when new routes are added. (though it is updated when new interfaces come online). This can cause a problem for tunneling interfaces that set up a direct route to the host before coming online using proto_add_host_dependency

@feckert - feel free to assign to me. Working on a fix for this now.

@aaronjg
Copy link
Contributor Author

aaronjg commented Aug 30, 2020

With a faster startup, this seems more likely to occur than before, so I added a fix to: #13169 by having rtmon update the ipsets when new routes are added/deleted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant