-
Notifications
You must be signed in to change notification settings - Fork 834
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
Mirrored networking mode is not supported, falling back to NAT networking #11899
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 View similar issuesPlease view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it! Open similar issues:
Closed similar issues:
|
I cannot provide logs since I do not have administrator priviliges. |
Unfortunately without logs we can't investigate the issue. Closing for now. Feel free to reopen if you can collect logs. |
Windows Version
Microsoft Windows [Version 22631.3007]
WSL Version
2.2.4.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.153.1-microsoft-standard-WSL2
Distro Version
Ubuntu 24.04
Other Software
Repro Steps
[boot]
systemd=true
autoProxy=true
Expected Behavior
Network works.
Actual Behavior
Network doesnt work, connection timed out.
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: