-
Notifications
You must be signed in to change notification settings - Fork 849
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
Support networkingMode=mirrored
while IPv6 is disabled via Registry
#12480
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The script will output the path of the log file once done. If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here Once completed please upload the output files to this Github issue. Click here for more info on logging |
/feature |
Diagnostic information
|
Hi there. WSL fully supports disabling IPv6 using Powershell NetAdapterBinding commandlets. https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/configure-ipv6-in-windows "Run the PowerShell command Disable-NetAdapterBinding -Name "" -ComponentID ms_tcpip[6]" |
Is your feature request related to a problem? Please describe.
In previous issues we discovered that having
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents
set to0xFF / 255
is problematic whennetworkingMode=mirrored
is used - networking Mode simply falls back to the bridged default networking under windows. Sometimes removing or setting to0x20
is helpful and users are permanently happy. Sometimes that is not enough - IPv6 Registry Setting related Issues .It seems that - either because of past windows vulnerability mitigations or caused by a VPN Client - a lot of folks do not have the ability to reliably set that registry value without it being reset the next reboot.
Describe the solution you'd like
It would be neat if WSL in this case would just do the mirrored mode networking without IPv6.
Describe alternatives you've considered
It'd be neat if Microsoft could do some work to get IT administrators to get rid of the vulnerability mitigation when it is no longer needed though that isn't the WSL teams problem to deal with.
The text was updated successfully, but these errors were encountered: