Fix so_original_dst retrieval in dual-stack mode #2841
Merged
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.
In 9ee109a we generalized the
so_original_dst
function to first retrieve the socket'sSO_DOMAIN
in order to determine what constants to use to retrieve the original destination, that would work for both IP families.This works fine when the socket is bound to
0.0.0.0
and receives a connection to the pod's IPv4 address, or when bound to::
and receives a connection to the pod's IPv6 address. When the cluster is in dual-stack mode and we bind the socket to::
, it properly receives connections targeted at both the pod's IPv4 and IPv6 addresses, but in the former case thegetsockopt
call to retrieve the original destination fails with:The problem is that in this case we're dealing with an IPv4-mapped IPv6 address so
SO_DOMAIN
returnsAF_INET6
but apparently in this case we requireAF_INET
when interrogatinggetsockopt
for the original destination.To fix, instead of asking for
SO_DOMAIN
we determine the peer's IP family and use that to set the appropriate constants forgetsocketopt
.