Ping/MTR packet loss with traffic looping back to WSL with every hop.

[gary-ovh]

Windows Build Number

Microsoft Windows [Version 10.0.19042.985]

WSL Version

• WSL 2
• WSL 1

Kernel Version

5.4.72

Distro Version

Ubuntu 20.04

Other Software

My traceroute v0.93

Repro Steps

I am just going traceroutes and ping tests to other sites and I am only getting weird traces and packet loss in WSL.

mtr google.ca

Expected Behavior

The route should reach the destination without loss.

Actual Behavior

Getting 25% or more packet loss. Appears traffic is looping back to WSL with every hop.

Diagnostic Logs

$mtr google.ca
 Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. LWI376877.mshome.net                                                      7.4%    95    8.0 679.0   0.2 2983. 904.7
    172.22.153.108
 2. 149.56.136.125                                                            6.3%    95   17.3 657.5  11.3 2870. 864.7
    172.217.13.99
    172.22.153.108
 3. be123.bhs-d1-a75.qc.ca                                                    6.3%    95   18.9 694.3  11.6 3145. 911.9
    172.217.13.99
    172.22.153.108
 4. 10.95.81.8                                                                6.3%    95   17.2 699.5  12.7 3112. 916.3
    172.217.13.99
    172.22.153.108
 5. 142.44.208.172                                                            6.3%    95   15.5 651.1  13.7 3001. 876.2
    172.217.13.99
    172.22.153.108
 6. (no route to host)

$ip a s dev eth0

4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:15:5d:3b:85:07 brd ff:ff:ff:ff:ff:ff
    inet 172.22.153.108/20 brd 172.22.159.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::215:5dff:fe3b:8507/64 scope link
       valid_lft forever preferred_lft forever

$ip r
default via 172.22.144.1 dev eth0 linkdown
172.22.144.0/20 dev eth0 proto kernel scope link src 172.22.153.108 linkdown

[gary-ovh]

Issue seems fine today. I will close this for now.

Strangely the issue was happening when connected or not connected to VPN, but only occurring on WSL.