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

wsl2的ipv6无法访问 #11610

Closed
1 of 2 tasks
AntyRia opened this issue May 23, 2024 · 4 comments
Closed
1 of 2 tasks

wsl2的ipv6无法访问 #11610

AntyRia opened this issue May 23, 2024 · 4 comments

Comments

@AntyRia
Copy link

AntyRia commented May 23, 2024

Windows Version

Microsoft Windows [版本 10.0.22621.3593]

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.153.1-2 WSLg

Distro Version

Ubantu22.04

Other Software

docker desktop 4.27.2

Repro Steps

1.配置.wslconfig如下:
[wsl2] memory=8GB processors=8 autoProxy=true ipv6=true [experimental] autoMemoryReclaim=gradual networkingMode=mirrored dnsTunneling=true firewall=true sparseVhd=true hostAddressLoopback=true
2.在wsl2中写一个测试脚本
`
from flask import Flask, jsonify

app = Flask(name)

@app.route('/ping', methods=['GET'])
def ping():
return jsonify({'message': 'Pong! API is up and running.'}), 200

if name == 'main':
app.run(debug=True, host='::', port=16001)
`
运行上述代码可以看到代码已经正常启动了:
image
3.通过ip addr在宿主机查看ip,获得一个ipv4地址和一个ipv6地址,分别测试,发现只有ipv4地址能够访问
image
image

Expected Behavior

我希望能够通过ipv6地址访问成功

Actual Behavior

现在wsl2中无法通过ipv6访问,关于防火墙等相关操作我已经检查过,当我在宿主机上运行这个python脚本时,一切正常

Diagnostic Logs

No response

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 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
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.

@AntyRia
Copy link
Author

AntyRia commented May 23, 2024

Copy link

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information
.wslconfig found
Detected appx version: 2.2.4.0
Found no WSL traces in the logs

Copy link
Contributor

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant