Handle edge cases in interface and routing config #1136
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.
The pull requests fixes two issues with very special configurations:
Here an example of such a fringe configuration:
interface Config (excerpt):
routes (excerpt):
With this configuration, the source address for the interfaces
10
and11
will return the link local address of the interface.The default route will return
192.168.155.1
which is only the second in the list.Both issues are addressed in this pull request.
Cheers,
Carsten