Skip to content

Support multi-connect on non-dual-mode IPv6#129892

Open
am11 wants to merge 4 commits into
dotnet:mainfrom
am11:patch-55
Open

Support multi-connect on non-dual-mode IPv6#129892
am11 wants to merge 4 commits into
dotnet:mainfrom
am11:patch-55

Conversation

@am11

@am11 am11 commented Jun 26, 2026

Copy link
Copy Markdown
Member

On operating systems like OpenBSD and WASI where IPv6 dual-mode isn't supported, a single socket can't reach both address families, so we re-create the still-unconnected handle for the current address' family to let the connect proceed. Since WASI doesn't use this handler, the gap never surfaced until OpenBSD end-to-end testing with TLS endpoints (dotnet restore failed with HttpRequestException hr=0x80004005; workaround DOTNET_SYSTEM_NET_DISABLEIPV6=1 dotnet restore did the trick and led to this fix)

@dotnet-policy-service dotnet-policy-service Bot added the community-contribution Indicates that the PR has been added by a community member label Jun 26, 2026
@dotnet-policy-service

Copy link
Copy Markdown
Contributor

Tagging subscribers to this area: @karelz, @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

@am11

am11 commented Jun 26, 2026

Copy link
Copy Markdown
Member Author

cc @rzikm, I tested it on OpenBSD box, it fixed the HttpRequestException mentioned above.

@rzikm rzikm requested a review from a team June 26, 2026 14:50
@am11 am11 added the os-openbsd OpenBSD OS, currently not officially supported label Jun 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-System.Net.Sockets community-contribution Indicates that the PR has been added by a community member os-openbsd OpenBSD OS, currently not officially supported

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant