Add route_check.py support for IPv4-mapped IPv6 addresses #3777
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)