Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

net: adjust support for dragonfly kernels not support ipv6 ipv4-mapped address #10764

Closed
mikioh opened this issue May 9, 2015 · 3 comments

Comments

Projects
None yet
2 participants
@mikioh
Copy link
Contributor

commented May 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.

@mikioh

This comment has been minimized.

Copy link
Contributor Author

commented May 9, 2015

And Listen{,TCP,UDP} would not work consistently on some released kernels (4.0.x maybe?) and upcoming kernels.

@mikioh

This comment has been minimized.

Copy link
Contributor Author

commented May 12, 2015

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.

@gopherbot

This comment has been minimized.

Copy link

commented May 14, 2015

CL https://golang.org/cl/10071 mentions this issue.

@mikioh mikioh closed this in eeb64b7 May 23, 2015

@mikioh mikioh removed their assignment May 27, 2015

@golang golang locked and limited conversation to collaborators Jun 25, 2016

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.