Expose a global switch to disable IPV6 #55012
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Tagging subscribers to this area: @dotnet/ncl Issue DetailsFixes #47583. Resolves #52287, #54807 and similar issues. Introduces an AppContext switch For consistency, this switch also impacts NameResolution and Ping, not only Sockets.
|
stephentoub
reviewed
Jul 1, 2021
src/libraries/Common/src/System/Net/SocketProtocolSupportPal.cs
Outdated
Show resolved
Hide resolved
stephentoub
reviewed
Jul 1, 2021
src/libraries/Common/src/System/Net/SocketProtocolSupportPal.cs
Outdated
Show resolved
Hide resolved
geoffkizer
approved these changes
Jul 1, 2021
Contributor
Author
|
|
stephentoub
approved these changes
Jul 9, 2021
This was referenced Jul 28, 2021
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #47583. Resolves #52287, #54807 and similar issues, without changing customer application code.
Introduces an AppContext switch
System.Net.DisableIPv6and environment variableDOTNET_SYSTEM_NET_DISABLEIPV6to emulate the lack of OS-level IPv6 support. This is useful to workaround dual-stack socket issues when the OS reports support of IPv6, but some other underlying infrastructure element (typically VPN) doesn't function well with IPv6 request.For consistency, this switch also impacts NameResolution and Ping, not only Sockets.