Severe performance degradation in Windows–WSL communication when using mirrored networking mode

[BBoomoom]

Windows Version

Microsoft Windows [Version 10.0.22631.5624]

WSL Version

2.6.3.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.6.87.2-1

Distro Version

Ubuntu 24.04

Other Software

vscode, gazebo

Repro Steps

1. Enable mirrored networking mode in WSL configuration
2. Restart WSL
3. Open a WSL project using VS Code Remote or run a gazebo simulation

Expected Behavior

Communication between Windows and WSL should remain responsive and performant regardless of the selected networking mode.

Actual Behavior

With mirrored networking enabled, communication becomes abnormally slow

• vscode remote takes 2-3 minutes to become operable
• simulation becomes laggy and sometimes crashes

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-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues

Once completed please upload the output files to this GitHub issue.

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.