Support scope_id for link-local IPv6 (rfc4007) #56807
Open
+44
−28
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
vchuravy
added
minor change
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.
IPv6 has a notion of link-local addresses (see https://www.rfc-editor.org/rfc/rfc4007),
I found https://labs.ripe.net/author/philip_homburg/whats-the-deal-with-ipv6-link-local-addresses/
helpful for further explanation.
Python uses
(host, port, flowinfo, scope_id)withflowinfoandscope_idbeing optional.The concrete scenario I was running into was receiving a broadcast packet and not being able
to connect to the sender since it was using link-local addresses.