Skip to content
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

Closed
1 of 2 tasks
trite2k3 opened this issue Aug 8, 2024 · 3 comments
Closed
1 of 2 tasks

Comments

@trite2k3
Copy link

trite2k3 commented Aug 8, 2024

Windows Version

Microsoft Windows [Version 22631.3007]

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

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

Copy link

github-actions bot commented Aug 8, 2024

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

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
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please 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:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@trite2k3
Copy link
Author

trite2k3 commented Aug 8, 2024

I cannot provide logs since I do not have administrator priviliges.

@OneBlue
Copy link
Collaborator

OneBlue commented Aug 8, 2024

Unfortunately without logs we can't investigate the issue. Closing for now. Feel free to reopen if you can collect logs.

@OneBlue OneBlue closed this as completed Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants