Add route_check.py support for IPv4-mapped IPv6 addresses #3777
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
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
The IPv4-mapped IPv6 address format differs between IP addresses and routes. * For IP addresses, the format is represented in hexadecimal (e.g., ::ffff:a1b:bd11). * For routes, the automated generation uses dotted decimal notation (e.g., ::ffff:10.27.189.17). Previously, route_check.py would generate warning logs due to mismatches between the interface table and the route table caused by these format differences. This commit updates route_check.py to handle IPv4-mapped IPv6 addresses consistently, ensuring that both formats are treated as equivalent values. Signed-off-by: gord_chen <[email protected]>
gord1306
force-pushed
the
ipv4_mapped_ipv6_route_check
branch
from
3964d81 to
c6691f7
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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.
The IPv4-mapped IPv6 address format differs between IP addresses and routes.
What I did
Previously, route_check.py would generate warning logs due to mismatches between the interface table and the route table caused by these format differences.
How I did it
This commit updates route_check.py to handle IPv4-mapped IPv6 addresses consistently, ensuring that both formats are treated as equivalent values.
How to verify it
Add new test data to verify the interface with IPv4-mapped IPv6 address
Previous command output (if the output of a command-line utility has changed)
New command output (if the output of a command-line utility has changed)