Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

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

Closed
AnakinShieh opened this issue Jul 23, 2024 · 3 comments
Closed

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

AnakinShieh opened this issue Jul 23, 2024 · 3 comments
Labels

Comments

@AnakinShieh
Copy link

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
Copy link

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.

@AnakinShieh
Copy link
Author

/question

Copy link

Diagnostic information
Found '/question', adding tag 'question'

@microsoft microsoft locked and limited conversation to collaborators Jul 26, 2024
@benhillis benhillis converted this issue into discussion #11842 Jul 26, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
Projects
None yet
Development

No branches or pull requests

1 participant