net: adjust support for dragonfly kernels not support ipv6 ipv4-mapped address #10764
Labels
Milestone
Comments
This was referenced May 9, 2015
And Listen{,TCP,UDP} would not work consistently on some released kernels (4.0.x maybe?) and upcoming kernels. |
Aha, on some 4.0.x version, setsockopt(IPV6_V6ONLY=0) finishes successfully but the kernel just pretends so, actually the kernel ignores that request and the state is still IPV6_V6ONLY=1. |
CL https://golang.org/cl/10071 mentions this issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Not sure the version of dragonfly builder but the root cause of test flakiness comes from the kernel changes like the following:
http://gitweb.dragonflybsd.org/dragonfly.git/commit/727ccde8cce813911d885b7f6ed749dcea68a886
Simply dragonfly is dropping support for ipv6 ipv4-mapped address for some reason.
The text was updated successfully, but these errors were encountered: