Diagnostics complets WSL2 — Réseau cassé

[InfograDuck]

Windows Version

Windows 11 Famille 25H2 — Build 26200.7922

WSL Version

Version WSL : 2.6.3.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

Distribution par défaut : Ubuntu Version par défaut : 2

Distro Version

No LSB modules are available. Release: 24.04

Other Software

• VScode running wsl : ubuntu
• taiscale

Repro Steps

wslconfig : nat -> VITE working, copilot does not.
mirrored -> copilot working, VITE not

Expected Behavior

WSL connected to internet; ping without loss

Actual Behavior

ERR_CONNEXION_TIMEOUT

Diagnostic Logs

Diagnostics complets WSL2 — Réseau cassé

Machine

• OS : Windows 11 Famille 25H2 — Build 26200.7922
• PC : ASUS (VivoBook Pro)
• Réseau Windows : Fonctionne normalement (Wi-Fi MediaTek MT7921)
• WSL : Ubuntu (WSL2)
• Adaptateurs réseau : vEthernet WSL (Hyper-V), Tailscale, AnchorFree TAP-Windows V9, Bluetooth

Symptôme

• ping 8.8.8.8 depuis WSL2 → 100% packet loss systématique
• ping 192.168.16.1 (gateway WSL) → 100% packet loss aussi
• Windows a Internet, WSL2 n'en a aucun

Diagnostics collectés

Commande | Résultat -- | -- ip route (WSL) | default via 192.168.16.1 dev eth0 ip addr (WSL) | 192.168.26.130/20 sur eth0 cat /etc/resolv.conf | nameserver 10.255.255.254 arp -a (WSL) | Gateway 192.168.16.1 → MAC 00:15:5d:dc:8c:03 (résolu mais ne répond pas) Get-NetIPAddress *WSL* (Windows) | 192.168.16.1/20 sur vEthernet WSL — correct Get-NetIPInterface *WSL* (Windows) | Forwarding = Disabled (activé manuellement → aucun effet) route print \| findstr 192.168 (Windows) | Aucune route vers le subnet WSL Programme Windows Insider | Non inscrit

Tentatives effectuées (toutes échouées)

1. ✗ Mode mirrored dans .wslconfig → Vite inaccessible, pas d'Internet
2. ✗ Mode NAT dans .wslconfig → 100% packet loss
3. ✗ wsl --shutdown + relance (plusieurs fois)
4. ✗ Restart-Service hns
5. ✗ netsh winsock reset + netsh int ip reset all + reboot (×2)
6. ✗ ipconfig /flushdns + /release + /renew
7. ✗ Set-NetIPInterface -Forwarding Enabled sur vEthernet WSL
8. ✗ wsl-vpnkit (importé et lancé → même 100% loss)
9. ✗ Désactivation AnchorFree TAP adapter → aucun changement
10. ✗ Changement MTU → aucun effet

État actuel nettoyé

• wsl-vpnkit désinstallé
• Forwarding remis à Disabled
• .wslconfig : uniquement localhostForwarding=true
• AnchorFree TAP réactivé
• Aucune modification persistante

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