Initial passive BMP support #223
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Gunna need to add authentication next.. |
|
Just checking your pulse on this before working about resolving conflicts.. I'm using this codebase extensively from an image built from my branch very successfully towards many Juniper routers. I can extol the benefits here, along with vendor/RFC support, and that it's an optional backwards compatible change, but in the end it would need your approval. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR is an initial iteration to support passive outbound BMP connections as a backwards-compatible option when initializing the BMP server (see #220 for reference). As stated in the issue thread, the RFC defines support for passive connections and is supported by major routing device vendors (e.g. Arista and Juniper).
The initial approach is simplistic, but my plan would be to support for multiple routers to establish multiple connections in parallel or failover schemas.