Mirrored mode "required features"

[quarrel]

Windows Version

Microsoft Windows [Version 10.0.22631.4037]

WSL Version

2.3.17.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.10.3

Distro Version

Ubuntu 24.10

Other Software

No response

Repro Steps

When first set up, mirrored mode was working as expected.

Since (I think?) my last WSL upgrade (via "wsl --update --pre-release"), when first launching a shell I see:

"
wsl: Mirrored networking mode is not supported: Windows version 22631.4037 does not have the required features.
Falling back to NAT networking.
"

NAT networking works as expected, but mirrored is, well, better.

Mirrored is set via a .wslconfig, which hasn't changed since it was working.

Afaik my Win11 build hasn't recently changed (since KB5041585 was installed 14 August 24), nor have I knowingly disabled any Win11 features that WSL should rely on (although is there any easy way for me to check?). In any event, the docs suggest that anything higher than 22H2 should have the required features.

Expected Behavior

Mirrored mode should work.

Actual Behavior

Mirrored mode does not work.

Diagnostic Logs

No response

[github-actions]

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

• networkMode=mirrored gives an error (#11359), similarity score: 0.77

Closed similar issues:

• Mirrored mode networking unavailable in Windows 11 (#11414), similarity score: 0.82
• Can't use mirrored: Says it's not supported (#11331), similarity score: 0.81
• wsl: Mirrored networking mode is not supported, falling back to NAT networking (#11283), similarity score: 0.77
• Mirrored networking mode is not supported, falling back to NAT (#11332), similarity score: 0.76

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

[quarrel]

See attached logs from collect-networking-logs.ps1

WslNetworkingLogs-2024-08-23_14-12-07.zip

[github-actions]

Diagnostic information

.wslconfig found
	Custom kernel found: 'C:\Users\daz\wsl2\bzImage'
Detected appx version: 2.3.17.0
optional-components.txt not found

[quarrel]

Since a recent reboot, I can no longer reproduce this error.

I have almost always used WSL (and mirrored mode) on a wired ethernet connection that does not change.

I have recently been travelling and exclusively on wifi, oft-times with changing wifi networks through my day.

If I had to guess, this error was produced because of this change, but it is just a hunch given my recent change in usage.

In any event, the error message seems unhelpful or incorrect, however I triggered it.

I'll see if I can reproduce it over the coming days, or otherwise gain any further insight.

[CatalinFetoiu]

thanks for reporting the issue
if you are able to repro again, please collect networking logs using instructions at https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues

the script will create a zip with name starting with "WslNetworkingLogs"

[jamesalucas]

I had the same issue, running Windows 11 23H2 (same on both 22631.4027 and then 22631.4169) and I tried all sorts of fixes. The one that eventually worked was this one. So commenting here in case it helps someone else in the future. As soon as Get-NetFirewallHyperVPort worked, I stopped getting the error and mirrored networking worked as expected.