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

Use static routes to implement 'host' behavior for non-Linux devices #1710

Open
ipspace opened this issue Dec 30, 2024 · 2 comments
Open

Use static routes to implement 'host' behavior for non-Linux devices #1710

ipspace opened this issue Dec 30, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@ipspace
Copy link
Owner

ipspace commented Dec 30, 2024

Now that we have the generic static routing module and the code to generate the static routes toward the default gateway, we could implement 'role: host' for other devices. The only requirements would be that a device supports the 'routing.static' feature.

To further optimize the static routes, we could have "initial.mgmt_vrf" feature to indicate whether the device uses a management VRF. Such a device needs just a default route not a bunch of routes for pool prefixes.

@ipspace ipspace added the enhancement New feature or request label Dec 30, 2024
@jbemmel
Copy link
Collaborator

jbemmel commented Dec 30, 2024

We already have netlab_mgmt_vrf for frr, not exactly a feature but related

@ipspace
Copy link
Owner Author

ipspace commented Dec 31, 2024

We already have netlab_mgmt_vrf for frr, not exactly a feature but related

That would be a nice way to ensure someone using an old box/container would not complain -- create a bunch of static routes unless the node has netlab_mgmt_vrf set in which case use just a default route.

However, netlab_mgmt_vrf could be defined in a number of places, so it will be fun to figure out its final value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants