Intermittent networking issue on WSL to external IP

[DenisSa]

Environment

Microsoft Windows [Version 10.0.19042.804]
Ubuntu 20.04
Linux version 5.4.72-microsoft-standard-WSL2 (oe-user@oe-host) (gcc version 8.2.0 (GCC)) #1 SMP Wed Oct 28 23:40:43 UTC 2020
Dell XPS 7590 with Killer Wi-FI 6 AX1650x adapter

Hey guys, I'm experiencing intermittent connectivity issues from WSL2 (confirmed from both Ubuntu as well as clean install of OpenSuse 15.2) to both public and private IP addresses.
I have also confirmed that it's not a general networking issue by pinging from Windows, which works without an issue.

Hardware: Dell XPS 7590 with Killer Wi-FI 6 AX1650x adapter, connection is over WIFI.

sudo ping -f 192.168.1.100
[sudo] password for d:
PING 192.168.1.100 (192.168.1.100) 56(84) bytes of data.
.......E...............E.......E.......E.......E.......E.......E.......E.......E.......E.......E.......E.......E.^C
--- 192.168.1.100 ping statistics ---
15338 packets transmitted, 15225 received, +112 errors, 0.736732% packet loss, time 91642ms
rtt min/avg/max/mdev = 0.964/9.495/2099.945/116.095 ms, pipe 9, ipg/ewma 5.975/1.923 ms```

[Bartdoekemeijer]

I have been having similar issues. I'm trying to pin it down based on other issues raised in this repository. Do you have a VPN connected in Windows? On what Windows version are you, H2?

[DenisSa]

I do not have a VPN running actively, but I do have 2 adapters for VPNs installed (for Azure and AWS)
Version info below:

[mingsxs]

Hi, I am seeing a similar issue, but it just occurs when I want to use my laptop after an uncertain idle time (normally hours for a lunch break or overnight cause I never shutdown my laptop if not necessary). it looks like it will suffer some intermittent packet loss, but I tried the same address with windows ping or putty SSH, they work just fine.

[mingsxs]

BTW, I am using the WSL2 with Ubuntu-20.04 distribution, my win os build is 18636.1379, I believe everything regarding my windows network adapter driver as well WSL2 related stuff are up-to-date.

[mingsxs]

Hi, this issue still exists, I can paste some ping log, one is from my localhost windows, the other is from the WSL subsystem running on the same machine, the difference between these 2 obviously shows the intermittent packet loss.

• From Windows

PS C:\Users\ming1li2> ping -t srdcws1096.amd.com

Pinging srdcws1096.amd.com [10.66.16.4] with 32 bytes of data:
Reply from 10.66.16.4: bytes=32 time=4ms TTL=63
Reply from 10.66.16.4: bytes=32 time=5ms TTL=63
Reply from 10.66.16.4: bytes=32 time=5ms TTL=63
Reply from 10.66.16.4: bytes=32 time=3ms TTL=63
Reply from 10.66.16.4: bytes=32 time=3ms TTL=63
Reply from 10.66.16.4: bytes=32 time=2ms TTL=63
Reply from 10.66.16.4: bytes=32 time=3ms TTL=63
Reply from 10.66.16.4: bytes=32 time=3ms TTL=63
Reply from 10.66.16.4: bytes=32 time=2ms TTL=63
Reply from 10.66.16.4: bytes=32 time=3ms TTL=63
Reply from 10.66.16.4: bytes=32 time=2ms TTL=63
Reply from 10.66.16.4: bytes=32 time=4ms TTL=63
Reply from 10.66.16.4: bytes=32 time=3ms TTL=63
Reply from 10.66.16.4: bytes=32 time=2ms TTL=63
Reply from 10.66.16.4: bytes=32 time=3ms TTL=63
Reply from 10.66.16.4: bytes=32 time=3ms TTL=63
Reply from 10.66.16.4: bytes=32 time=3ms TTL=63
Reply from 10.66.16.4: bytes=32 time=50ms TTL=63
Reply from 10.66.16.4: bytes=32 time=2ms TTL=63
Reply from 10.66.16.4: bytes=32 time=3ms TTL=63
Reply from 10.66.16.4: bytes=32 time=3ms TTL=63
Reply from 10.66.16.4: bytes=32 time=2ms TTL=63
Reply from 10.66.16.4: bytes=32 time=3ms TTL=63
Reply from 10.66.16.4: bytes=32 time=3ms TTL=63

• From WSL Subsystem

❯ ping srdcws1096.amd.com
PING srdcws1096.amd.com (10.66.16.4) 56(84) bytes of data.
64 bytes from srdcws1096.amd.com (10.66.16.4): icmp_seq=1 ttl=62 time=2.64 ms
64 bytes from srdcws1096.amd.com (10.66.16.4): icmp_seq=2 ttl=62 time=2.76 ms
64 bytes from srdcws1096.amd.com (10.66.16.4): icmp_seq=3 ttl=62 time=2.98 ms
64 bytes from srdcws1096.amd.com (10.66.16.4): icmp_seq=4 ttl=62 time=3.32 ms
64 bytes from srdcws1096.amd.com (10.66.16.4): icmp_seq=6 ttl=62 time=3.21 ms
64 bytes from srdcws1096.amd.com (10.66.16.4): icmp_seq=7 ttl=62 time=3.30 ms
From 172.17.210.42 (172.17.210.42) icmp_seq=8 Destination Host Unreachable
From 172.17.210.42 (172.17.210.42) icmp_seq=9 Destination Host Unreachable
From 172.17.210.42 (172.17.210.42) icmp_seq=10 Destination Host Unreachable
64 bytes from srdcws1096.amd.com (10.66.16.4): icmp_seq=11 ttl=62 time=3.74 ms
64 bytes from srdcws1096.amd.com (10.66.16.4): icmp_seq=12 ttl=62 time=3.16 ms
64 bytes from srdcws1096.amd.com (10.66.16.4): icmp_seq=13 ttl=62 time=5.44 ms
64 bytes from srdcws1096.amd.com (10.66.16.4): icmp_seq=14 ttl=62 time=3.81 ms
64 bytes from srdcws1096.amd.com (10.66.16.4): icmp_seq=15 ttl=62 time=2108 ms
64 bytes from srdcws1096.amd.com (10.66.16.4): icmp_seq=16 ttl=62 time=1044 ms
64 bytes from srdcws1096.amd.com (10.66.16.4): icmp_seq=17 ttl=62 time=3.88 ms
64 bytes from srdcws1096.amd.com (10.66.16.4): icmp_seq=18 ttl=62 time=3.82 ms
64 bytes from srdcws1096.amd.com (10.66.16.4): icmp_seq=19 ttl=62 time=2082 ms
64 bytes from srdcws1096.amd.com (10.66.16.4): icmp_seq=20 ttl=62 time=1044 ms
64 bytes from srdcws1096.amd.com (10.66.16.4): icmp_seq=21 ttl=62 time=3.96 ms
64 bytes from srdcws1096.amd.com (10.66.16.4): icmp_seq=22 ttl=62 time=3.40 ms
From 172.17.210.42 (172.17.210.42) icmp_seq=23 Destination Host Unreachable
From 172.17.210.42 (172.17.210.42) icmp_seq=24 Destination Host Unreachable
From 172.17.210.42 (172.17.210.42) icmp_seq=25 Destination Host Unreachable
64 bytes from srdcws1096.amd.com (10.66.16.4): icmp_seq=26 ttl=62 time=3.57 ms

Those ping actions happened almost at the same time, you can clearly see the difference.

[markoueis]

I wonder if its related to this: docker/for-win#8861

[mingsxs]

Not really sure, but the scenario, as well as the behavior, very similiar.

[mingsxs]

Hi WSL official, I wonder if there is a schedule for this issue, cause honestly this issue could often be painful.

[mingsxs]

Hi, after upgrading to 20H2 version, I didn't see this issue.

[adamncasey]

I see this issue intermittently too on windows 10 1909. My ping output from PS/WSL2 looks identical to what was posted above: #6644 (comment)

Running wsl.exe --shutdown clears the fault.

[adamncasey]

This still occurs on 21H1

[microsoft-github-policy-service]

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

Thank you!