Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign upnet: adjust support for dragonfly kernels not support ipv6 ipv4-mapped address #10764
Comments
mikioh
added this to the Go1.5 milestone
May 9, 2015
This was referenced May 9, 2015
mikioh
added
the
OS-Dragonfly
label
May 9, 2015
This comment has been minimized.
This comment has been minimized.
|
And Listen{,TCP,UDP} would not work consistently on some released kernels (4.0.x maybe?) and upcoming kernels. |
This comment has been minimized.
This comment has been minimized.
|
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. |
mikioh
self-assigned this
May 12, 2015
mikioh
referenced this issue
May 14, 2015
Closed
net: TestDualStackUDPListener fails on dragonfly #10808
This comment has been minimized.
This comment has been minimized.
gopherbot
commented
May 14, 2015
|
CL https://golang.org/cl/10071 mentions this issue. |
mikioh
closed this
in
eeb64b7
May 23, 2015
mikioh
removed their assignment
May 27, 2015
golang
locked and limited conversation to collaborators
Jun 25, 2016
gopherbot
added
the
FrozenDueToAge
label
Jun 25, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
mikioh commentedMay 9, 2015
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.