WSL version 2 has no network connectivity, version 1 works alright

[PatrykSL]

Windows Version

Microsoft Windows 22H2 (19045.3930)

WSL Version

10.0.19041.3636 (WinBuild.160101.0800)

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.10.102.1

Distro Version

Ubuntu 22.04.3 LTS (GNU/Linux 5.10.102.1-microsoft-standard-WSL2 x86_64)

Other Software

Docker Desktop (Windows)

Repro Steps

Install fresh Ubuntu from Windows Store after setting default wsl version to 2.

Expected Behavior

I was expecting networking to function normally.

Actual Behavior

No internet connection on any WSL version 2 ubuntu distribution. When falling back to version 1- everything works fine. I tried to change nameserver to 8.8.8.8 as read in some bug reports but that doesn't work.

Diagnostic Logs

No logs needed. Just no network connectivity. When using command "ping 8.8.8.8" it shows --- 8.8.8.8 ping statistics ---
380 packets transmitted, 0 received, 100% packet loss, time 394155ms

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

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. Thank you!

Open similar issues:

• WSL 2 Network Connectivity Issue (#10433), similarity score: 0.88
• [WSL2] No network (#4731), similarity score: 0.87

Closed similar issues:

• the network of wsl2 does not work (#7421), similarity score: 0.87
• WSL 2 networking doesn't work at all for me (#5908), similarity score: 0.86
• Connectivity problems with WSL2 (#5881), similarity score: 0.86

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

[ghost]

If you add /logs and version information I will re-open and forward to the networking folks.

[PatrykSL]

WslLogs-2024-01-24_14-58-34.zip
As requested here are logs.

[PatrykSL]

And just now I did add a WSL Version info. Please open the issue.

[ghost]

Looks like you're using inbox WSL2. Do you get the same result if using WSL2 from the store?

[PatrykSL]

@pmartincic it's the same issue:

wsl: Nie można utworzyć punktu końcowego sieci o adresie: „172.28.92.148”, przypisano nowy adres: „172.23.175.62”
PATRYK-PC:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
^C
--- 8.8.8.8 ping statistics ---
20 packets transmitted, 0 packets received, 100% packet loss
PATRYK-PC:~#

[chanpreetdhanjal]

Hi. Can you please collect networking logs by following the instructions below?
https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues

[PatrykSL]

WslNetworkingLogs-2024-01-30_09-59-55.zip
@chanpreetdhanjal Hello, logs you requested are attached to this message

[supahfox]

@pmartincic I'm having the same issue
These are my logs WslLogs-2024-01-31_12-05-41.zip

WSL version: 2.0.14.0
Kernel version: 5.15.133.1-1

[alexrsagen]

Copying in my comment from #4731 to add context, a workaround and suggested solution.

I am experiencing the same issue on Windows 11 build 22000.3296 with WSL version 10.0.22621.2860 (WinBuild.160101.0800) and kernel version 5.10.102.1. I have isloated the problem and found a (bad) workaround. The issue is that the Hyper-V Default Switch used for WSL2 NAT networking selects/uses the wrong uplink interface, consistently.

In addition to a few different VPN interfaces (not relevant), I primarily use the on-board Ethernet interface for networking. I also have a PCIe-connected Wi-Fi card installed, which WSL2 consistently uses as the uplink interface (even when it is not connected to a Wi-Fi network) for reasons unknown to me.

List of things I have attempted which made no difference at all and did not solve the issue:

• Disable every network interface (Wi-Fi, VPNs) except the interface I want Hyper-V to use (Ethernet)
• netsh int ip reset, netsh winsock reset
• Uninstall Hyper-V, WSL and any related components, reboot, reinstall components
• Stop the services cmdservice, hns, vmcompute, lxssmanager and re-start those services

Workaround:

• Disable every network interface except the PCIe Wi-Fi card (important step, otherwise the default gateway will be reached through the on-board Ethernet, but Hyper-V will still attempt to use the Wi-Fi card which will not work)
• Connect to a Wi-Fi network

It is surprising to me that there is no option to select desired uplink network interface for the Hyper-V Default Switch or NAT solution. This would solve the issue.