-
Notifications
You must be signed in to change notification settings - Fork 822
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
In mirrored network mode, Devices on the same LAN subnet can access ports within my WSL2, but those on different subnets cannot. #11447
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 scipt will output the path of the log file once done. 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:
|
WslLogs-2024-04-11_10-51-37.zip I used nc to listen on port 6400 in WSL2 and attempted to telnet to it from devices on other subnets. However, this was unsuccessful. |
Diagnostic information
|
The issue was resolved after closing the VPN and uninstalling the virtual network adapter. |
Windows Version
10.0.22635.3430
WSL Version
2.2.1.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.150.1
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
Listening on port 6400 within WSL2, then attempting to telnet to this port from devices on different subnets.
Expected Behavior
devices from all subnets can telnet successfully.
Actual Behavior
My device's IP is 192.168.1.123. I can successfully telnet to 192.168.1.123 port 6400 from devices with IPs in the range of 192.168.1.x. However, devices in other ranges like 192.168.2.x cannot telnet successfully. But if I listen on port 6400 on Windows, devices from all subnets can telnet successfully.
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: