microsoft / WSL

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

WSL2 will occur network mirrored mode isn't supported, fallback to NAT mode #11333

Closed dnisqa closed 6 months ago

dnisqa commented 6 months ago

Windows Version

Micorsoft Windows 10 Pro [10.0.19045.4170]

WSL Version

2.1.5.0

Are you using WSL 1 or WSL 2?

Kernel Version

5.15.146.1@WSL2 4.4.0-19041@WSL1

Distro Version

Ubuntu 20.04 & 22.04

Other Software

No!

Repro Steps

.wslconfig is below [wsl2] memory=4G processors=2 networkingMode=mirrored dnsTunneling=true autoProxy=false ipv6=true

dhcp=false

localhostforwarding=true [experimental] sparseVhd=true firewall=false

Test 1 (WSL setup to version 2) wsl --set-default-version 2 wsl --install -d Ubuntu-22.04 Windows log will show

  1. Mirrored mode isn't support , fallback to NAT mode
  2. dnsTunneling isn't support WSL2-mirrored_dnsTunnel_not_support

wsl --shutdown wsl --unregister Ubuntu

Test 2 (WSL setup to version 1) wsl --set-default-version 1 wsl --install -d Ubuntu-22.04 Windows log doesn't show WSL warning message

Expected Behavior

WSL2 should support mirrored and dnsTunneling

Actual Behavior

Mirrored is not support DnsTunneling is not support

Diagnostic Logs

No response

github-actions[bot] commented 6 months ago

Hi I'm an AI powered bot that finds similar issues based off the issue title.

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. Thank you!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

craigloewen-msft commented 6 months ago

Please see the duplicated issues below, this is due to your Windows version not being correct. Please upgrade to Win11 latest and you should be able to use these features!

/dupe #11283

microsoft-github-policy-service[bot] commented 6 months ago

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!