Skip to content

/ go

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

Jump to bottom

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

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

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

mikioh opened this issue May 9, 2015 · 3 comments
Labels
FrozenDueToAge OS-Dragonfly
Milestone
Go1.5

Comments

@mikioh
Copy link
Contributor

@mikioh mikioh 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 mikioh added this to the Go1.5 milestone May 9, 2015
This was referenced May 9, 2015
Closed
Closed
@mikioh mikioh added the OS-Dragonfly label May 9, 2015
@mikioh
Copy link
Contributor Author

@mikioh mikioh commented May 9, 2015

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

@mikioh mikioh 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.
@mikioh mikioh self-assigned this May 12, 2015
@mikioh mikioh mentioned this issue May 14, 2015
Closed
@gopherbot
Copy link

@gopherbot gopherbot 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.
Assignees
No one assigned
Labels
FrozenDueToAge OS-Dragonfly
Projects
None yet
Milestone
Go1.5
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@mikioh @gopherbot
You can’t perform that action at this time.