mpls-conf: T915: Add LDP import and export control #639
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In this commit we added the ability to control import and export
of LDP FECs. This allows for an operator to specify which to
filter on ingress, and which to not announce on egress.
Change Summary
In this change we are adding more functionality to LDP. We are specifically adding the ability to control the import and export of the routes that LDP deals with. this shouldn't break any existing functionality.
Types of changes
Related Task(s)
https://phabricator.vyos.net/T915
Component(s) name
LDP
Proposed changes
We added the tie into FRR for access lists to be referenced and then added for import and export control. This functionality was added for both IPv4 and IPv6. Although the access list approach is a little bit cumbersome it does work as one expects.
How to test
I tested the changes in a GNS3 lab with Junipers and VyOS routers. The VyOS routers did correctly import and export the routes properly once the access list was properly configured. That all being said, configuring access lists for imports seems to work as one expects but seems unwieldy. It does work as expected though.
Checklist: