-
Notifications
You must be signed in to change notification settings - Fork 72
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
Ebgp unnumbered enhancements #362
Conversation
* Support interface-level underlay_as attributes
…ing a looped interface
Add ebgp unnumbered group with specific link-local-as as needed
I tried to keep the module attribute copying generic; the 'vrf' module attribute isn't strictly needed, but it gets included as the vrf module defines an interface level attribute Alternatively, we could introduce a 'neighbor_interface' category of attributes, containing the list of attributes to include in neighbor lists
|
No worries, it's perfectly OK to have remote interface attributes available in the neighbor list. Might come useful in other scenarios as well (example: check OSPF areas). |
This example is pushing the limits of what one might setup in a test topology, I wanted to see if I could do EBGP peering locally to leak routes between VRFs.
To make this work, I had to extend neighbor lists with module specific interface attributes ( bgp.underlay_as in this case )