search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.23k stars 808 forks source link

Is it possible to access WSL outside through ipv6? #11826

Closed AnakinShieh closed 1 month ago

AnakinShieh commented 1 month ago

I'm trying to access WSL like ssh remotely through ipv6 because I don't have a public ipv4 address, following configs like networkingMode=mirrored and hostAddressLoopback to enable ipv6 and expose wsl ports to windows and creating firewall rule for hyper-v to enable inbound rule for specific port (here, 22000 for SSH of WSL)1. But I still failed to establish ssh connection remotely/even locally through ipv6 address but successfully over ipv4 address. And at the same time, the ssh to windows ssh and a bridged-network virtual machine through ipv6 are all OK. While at the same time, I found it failed to access a ipv6 web server in WSL from Windows.

I'd like to know if it's possible to access WSL outside through ipv6, I haven't tried to disable networkingMode=mirrored and use netsh to create proxy v4 (WSL) to v6 (Windows) and don't know if it could work.

My current version and wsl conf is as follows,

WSL version: 2.2.4.0
Kernel version: 5.15.153.1-2
WSLg version: 1.0.61
MSRDC version: 1.2.5326
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26091.1-240325-1447.ge-release
Windows version: 10.0.22631.3880

wsl conf

[wsl2]
memory=180GB
networkingMode=mirrored
dnsTunneling=true

[experimental]
hostAddressLoopback=true
autoMemoryReclaim=gradual
github-actions[bot] commented 1 month ago

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](https://github.com/Microsoft/WSL/blob/master/diagnostics/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](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com 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.

AnakinShieh commented 1 month ago

/question

github-actions[bot] commented 1 month ago
Diagnostic information ``` Found '/question', adding tag 'question' ```