WSL - ping www.google.com - 100% packet loss

[AllanBernier]

Windows Version

Microsoft Windows [version 10.0.22631.3527]

WSL Version

Version WSL : 2.1.5.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.146.1-microsoft-standard-WSL2

Distro Version

Ubuntu-22.04

Other Software

No response

Repro Steps

ping www.google.com

Expected Behavior

$ping www.google.com

Envoi d’une requête 'ping' sur www.google.com [2a00:1450:4007:81a::2004] avec 32 octets de données :
Réponse de 2a00:1450:4007:81a::2004 : temps=31 ms
Réponse de 2a00:1450:4007:81a::2004 : temps=35 ms
Réponse de 2a00:1450:4007:81a::2004 : temps=36 ms
Réponse de 2a00:1450:4007:81a::2004 : temps=36 ms

Statistiques Ping pour 2a00:1450:4007:81a::2004:
    Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
    Minimum = 31ms, Maximum = 36ms, Moyenne = 34ms

Actual Behavior

$ping www.google.com

PING www.google.com (142.250.201.164) 56(84) bytes of data.
^C
--- www.google.com ping statistics ---
8 packets transmitted, 0 received, 100% packet loss, time 7243ms

Diagnostic Logs

cat /etc/wsl.conf

[boot]
systemd=true

cat /etc/resolv.conf

# This file was automatically generated by WSL. To stop automatic generation of this file, add the following entry to /etc/wsl.conf:
# [network]
# generateResolvConf = false
nameserver 192.168.176.1

ipconfig

Configuration IP de Windows


Carte réseau sans fil Connexion au réseau local* 1 :

   Statut du média. . . . . . . . . . . . : Média déconnecté
   Suffixe DNS propre à la connexion. . . :

Carte réseau sans fil Connexion au réseau local* 2 :

   Statut du média. . . . . . . . . . . . : Média déconnecté
   Suffixe DNS propre à la connexion. . . :

Carte réseau sans fil Wi-Fi :

   Suffixe DNS propre à la connexion. . . :
   Adresse IPv6. . . . . . . . . . . . . .: xxxx
   Adresse IPv6 temporaire . . . . . . . .: xxxx
   Adresse IPv6 de liaison locale. . . . .: xxxx
   Adresse IPv4. . . . . . . . . . . . . .: x.x.x.x
   Masque de sous-réseau. . . . . . . . . : 255.255.255.0
   Passerelle par défaut. . . . . . . . . : xxxxxx
                                       x.x.x.x

Carte Ethernet Connexion réseau Bluetooth :

   Statut du média. . . . . . . . . . . . : Média déconnecté
   Suffixe DNS propre à la connexion. . . :

Carte Ethernet vEthernet (WSL (Hyper-V firewall)) :

   Suffixe DNS propre à la connexion. . . :
   Adresse IPv6 de liaison locale. . . . .: fe80::e5dc:6d89:aa74:4e1d%31
   Adresse IPv4. . . . . . . . . . . . . .: 192.168.176.1
   Masque de sous-réseau. . . . . . . . . : 255.255.240.0
   Passerelle par défaut. . . . . . . . . :

[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 scipt will output the path of the log file once done.

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:

• WSL 2 Network Connectivity Issue (#10433), similarity score: 0.77

Closed similar issues:

• WSL2 Ping: 10%-12% packet loss (#7997), similarity score: 0.82
• Cannot ping both from Windows host and WSL (#8462), similarity score: 0.77
• Ping/MTR packet loss with traffic looping back to WSL with every hop. (#7036), similarity score: 0.76
• WSL failing to route network packets e.g. ping (#9818), similarity score: 0.76

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

[AllanBernier]

/question

[github-actions]

Diagnostic information

Found '/question', adding tag 'question'

[OneBlue]

/logs

[microsoft-github-policy-service]

Hello! Could you please provide more logs to help us better diagnose your issue?

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 scipt will output the path of the log file once done.

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.

Thank you!

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!