-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
fabricd: add option to treat dummy interfaces as loopback interfaces #18242
Conversation
324982e
to
f2cdb7a
Compare
can we separate out the zebra code changes to their own commit? It's a bit of logical code that is needed but not actually part of the fabricd changes. I would prefer that the code is broken up this way to allow for future understanding |
Introduce ZEBRA_IF_DUMMY interface flag to identify Linux dummy interfaces [0]. These interfaces behave similarly to loopback interfaces and can be specially handled by daemons. [0]: https://github.com/torvalds/linux/blob/master/drivers/net/dummy.c Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
done @donaldsharp. Let me know if there is anything else you need. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good ... there's one lint I think might need to be taken care of ...
|
Enable dummy-interfaces to be used as router-id interfaces in openfabric networks. This allows multiple openfabric routers with different router-ids on a single node when using IP unnumbered setup (interfaces without IPs configured). Previously we were limited by having a single loopback interface, allowing only one openfabric router per node. Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
Thanks for the review @riw777! Fixed the style issue. |
Add interface status flag for interfaces of type "dummy" 0. Add fabricd option to treat dummy interfaces as loopback interfaces.
This is a (kind of) continuation of #10679.
This patch enables dummy-interfaces to be used as router-id interfaces in openfabric networks. This allows us to have multiple openfabric routers with different router-id's on a single node when using a ip unnumbered setup (interfaces without ip's configured). Previously we were limited by only having a single loopback interface, meaning only a single openfabric router was possible.