-
Notifications
You must be signed in to change notification settings - Fork 830
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
With WSL2's Mirror Network Mode, Services on the Windows Host are Inaccessible, but the Reverse is Possible #12399
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:
|
Diagnostic information
|
I have looked at similar issues in this project and found a solution: enabling the WiFi hotspot on my laptop. I'm curious why this works. |
Windows Version
Microsoft Windows [Version 10.0.22631.4602]
WSL Version
2.3.26.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.167.4-1
Distro Version
Debian 12
Other Software
No response
Repro Steps
.wslconfig
is as follows, with other options set to default::python -m http.server 8000
in a directory only containing an index.html file:wget 127.0.0.1:8000
I tested all available network modes in WSL2. I was able to access the host service using both NAT and virtioProxy, but mirror mode (using 127.0.0.1) did not work.
However, when I run the command
python3 -m http.server 8100
in the WSL2 distro and then runwget 127.0.0.1:8100
in PowerShell, it works fine.Interestingly, on another laptop with the same WSL2 and Windows version, the setup works as expected. I'm confident the issue lies with some misconfiguration, but despite trying various approaches, I haven't been able to resolve it.
Expected Behavior
in WSL2: run command wget 127.0.0.1:8000 it works fine.
Actual Behavior
Connecting to 127.0.0.1:8000...
Diagnostic Logs
_No responseWslLogs-2024-12-21_12-17-00.zip
WslNetworkingLogs-2024-12-21_12-18-20.zip
_
The text was updated successfully, but these errors were encountered: