Allow IPv6 compat addresses (4in6) when parsing TCPv6 in V1 header #92
Closed
Freeaqingme wants to merge 3 commits intopires:mainfrom
Closed
Allow IPv6 compat addresses (4in6) when parsing TCPv6 in V1 header #92Freeaqingme wants to merge 3 commits intopires:mainfrom
Freeaqingme wants to merge 3 commits intopires:mainfrom
Conversation
Addresses like 0:0:0:0:0:ffff:7f00:1 should be allowed when parsing IPv6 protocols.
Owner
|
Maybe it's a good time to introduce https://pkg.go.dev/net/netip#Addr.Is4In6? |
This file contains hidden or 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
4 participants
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.
This is a follow-up on MR #49 by @emersion . All credits should go to him :)
I had a need to parse 4in6 addresses myself as well, so I took his MR as a starting point and took it from there. I have not yet tested this code in production, but I figured I'd already turn it into a PR.
There is one issue that I had to sort of work around: In the default net.IP library, an IPv4 address is (or can be) stored more or less in the same way an IPv6 address is stored with a ::FFFF: prefix. As such, there's no way to make a distinction based on a net.IP object if it was an IPv4 address, or IPv6 4in6 address.