Network crashed after using VSCode WSL plugin connected to container

[KawaiiZapic]

Windows Version

Microsoft Windows [Version 10.0.26200.8246]

WSL Version

2.7.1.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.6.114.1-1

Distro Version

Ubuntu-24.04

Other Software

Visual Studio Code 1.119.0 with WSL plugin 0.104.3

Repro Steps

1. Connect to WSL with VSCode WSL

Expected Behavior

Nothing should happend.

Actual Behavior

Network become extremly slow both on host and inside WSL, packet lossing rate and latency increase significantly when pinging gateway of my home network, at this stage it's recoverable by executing wsl --shutdown.
If ignoring this situation, after a few minutes, network card will stop working, the WLAN icon disappear from notification area, any attempts try to adjust network settings, include Settings App of Windows, quick network settings in notification area, will result a hang of the app or explorer.exe, can't poweroff or restarting system, Windows will stuck at "Restarting" or "Shutting down", only can recover by performance a hard power reset by long pressing power button.

Diagnostic Logs

Not collected yet, I need to submit this issue first. I had to performace a hard reset after I try to reproduce this issue

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

[KawaiiZapic]

/emailed-logs

[github-actions]

Diagnostic information

Found '/emailed-logs', adding tag 'emailed-logs'

[KawaiiZapic]

This issues can be alleviated by using VitrioProxy network mode and disable localhost forwarding, and only can be alleviated by set this 2 options together, try to enable localhost forwarding or use other network mode will cause this problem

[FetoiuCatalin]

Zapic (@KawaiiZapic) , thanks for the report. could you please collect networking logs during the repro, using the steps at https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-recommended-method

.\collect-wsl-logs.ps1 -LogProfile networking

[FetoiuCatalin]

Zapic (@KawaiiZapic) sorry, I realized you already sent some over email, let me take a look at those first

[KawaiiZapic]

@KawaiiZapic sorry, I realized you already sent some over email, let me take a look at those first

The log i sent over email only reproduced increased latency and packet lossing, can I send another log that reproducted address includes network card stop working to same email?

[FetoiuCatalin]

Zapic (@KawaiiZapic) yes please, if you have another one feel free to send it on the same email. thanks