Migrate IXPs from Quagga to FRR #46
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
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.
To help future-proof the mini Internet project, it would make sense to migrate from Quagga to FRR for the route server.
Most of the changes come from a draft that was already present within the IXP Dockerfile. The remaining changes in the router config are related to the command syntax difference between Quagga and FRR.
It's important to note that this migration requires the routers connected to the IXP needs to include the
no neighbor IXP enforce-first-asas documented here. Without this, the router will deny updates received from the IXP as it does not list its AS number at the beginning of the AS_PATH. This means that any course content will also need to be updated to reflect this.