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

vmadm route order can cause problems w/ complex network setups #757

Licenser opened this Issue Jan 4, 2018 · 0 comments


None yet
1 participant

Licenser commented Jan 4, 2018

With more complex network setups where a interfaces route is required to reach the default gateway vmadm's order of setting up routes is problematic.

The issue is that when the gateways get added before the interface route and route refuses to add it so it ends up missing.

We encountered the same issue with rvmadm for FreeBSD the solution we came up with is that the interface routes have to be added before any default or other routes, that way it's guaranteed that interface routes exist before other routs are added. This also seems to be the behavior that route itself has when adding routs with -p.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment