No network connectivity with networkingMode mirrored

[MHHenriksen]

Windows Version

Microsoft Windows [Version 10.0.26100.3037]

WSL Version

2.3.26.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

Linux version 5.15.167.4-microsoft-standard-WSL2 (root@f9c826d3017f)

Distro Version

Ubuntu 22.04

Other Software

VS Code 1.96.4
Extensions:

• WSL 0.88.5
• Docker 1.29.4
• Devcontainers 0.394.0
  Docker 27.2.0, build 3ab4256 (installed into WSL by devcontainers extension last year)
  Also been playing with the devontainer feature docker-in-docker, which may or may not have polluted my wsl network config.

Repro Steps

In ~/.wslconfig: (commented settings were also tried with no effect)

[wsl2]
networkingMode=mirrored
#dnsTunneling=true

[experimental]
#autoMemoryReclaim=gradual
#hostAddressLoopback=true

wsl --shutdown then wsl then:

Expected Behavior

Able to talk to the internet and intranet (which works with regular NAT networking mode)

Actual Behavior

# names have been anonymized
devcontainers@my-laptop:/mnt/d$ curl google.com
curl: (6) Could not resolve host: google.com
devcontainers@my-laptop:/mnt/d$ curl gitlab.corp.internal
curl: (6) Could not resolve host: gitlab.corp.internal
devcontainers@my-laptop:/mnt/d$ ping 8.8.8.8
ping: connect: Network is unreachable

Diagnostic Logs

WslNetworkingLogs-2025-02-05_10-16-24.zip

[github-actions]

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:

• No network access with networkingMode=mirrored (#10791), similarity score: 0.87
• Mirrored networking fine at first but drops after only a few minutes (#11369), similarity score: 0.83
• Network is unreachable with networking Mode=mirrored (#12515), similarity score: 0.83
• With WSL2's Mirror Network Mode, Services on the Windows Host are Inaccessible, but the Reverse is Possible (#12399), similarity score: 0.82

Closed similar issues:

• Networking mode does not work in mirrored mode (#11540), similarity score: 0.82

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

Diagnostic information

Found '/feature', adding tag 'feature'
.wslconfig found
Detected appx version: 2.3.26.0
optional-components.txt not found

[MHHenriksen]

Maybe it's also worth mentioning that my Windows and Hyper-V networking stack might have leftover garbage in it from tons of unrelated HCI VM experiments, that could be interfering with whatever autodetect magic is done by wsl. Let me know if and how I can provide more details if interested.

[CatalinFetoiu]

thanks for reporting the issue and attaching logs - in the logs I do not see any Windows interface mirrored in Linux, in the Linux interfaces there are only some br, veth interfaces and a docker0 interface.

Could you please do the following to collect a new set of logs? We want to capture the logs while WSL is starting up, to see if there is something wrong while interfaces are mirrored.

.\collect-networking-logs.ps1 -RestartWslReproMode
start WSL and confirm the issue is present
stop log collection

[MHHenriksen]

The new log archive fails to upload directly, so emailing separately as per CONTRIBUTING.md

Also, the -RestartWslReproMode param isn't a flag so the full command needed was .\collect-networking-logs.ps1 -RestartWslReproMode $true

Still repros the same. Hope the new logs help, thanks for investigating!