WSL networking stopped working

[krippix]

Windows Version

Microsoft Windows [Version 10.0.22621.1413]

WSL Version

1.1.6.0

Are you using WSL 1 or WSL 2?

WSL 2

Kernel Version

5.15.90.1

Distro Version

Ubuntu 22.04 / Debian 11.6

Other Software

No response

Repro Steps

• Attempt any kind of communication outside of the WSL network

Expected Behavior

WSL reacts to incoming packages

Actual Behavior

WSL seems to ignore any incoming packages.

• Any attempt to communicate with anything that isn't the IP address of the host system fails.
• The packages DO reach their destination and replys seem to reach wsl (at least thats what it looks like in Wireshark)
• BUT it seems like WSL ignores any replies
• Reinstalling the wsl feature or the distributions did not fix the issue.

Diagnostic Logs

Sent via feedback-hub as the logfile generated from the script got quite large.

Example when pinging google.com (note that DNS does work):

Update: 05 July 2023

Downgrading my Ubuntu WSL instance to WSL1 fixed the issue there. But WSL2 still refuses to do so.

[Biswa96]

Could you check if running the following command fixes the issue?

echo nameserver 1.1.1.1 | sudo tee /etc/resolv.conf

[krippix]

Could you check if running the following command fixes the issue?

echo nameserver 1.1.1.1 | sudo tee /etc/resolv.conf

Unfortunately this will only make the problem worse, as DNS does work.

[TechnoTaff]

Seeing this exact same issue

WSL version: 1.2.2.0
Kernel version: 5.15.90.1
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.525

I've tried everything I can think of, just like @krippix I can see the packets return from their destination but it's like the Ubuntu install is ignoring them. The weird thing is DNS is resolving fine:

me@thispc:~$ nslookup www.google.com
Server:         172.21.96.1
Address:        172.21.96.1#53

Non-authoritative answer:
Name:   www.google.com
Address: 172.217.169.36
Name:   www.google.com
Address: 2a00:1450:4009:818::2004

[TechnoTaff]

Now I feel like i'm losing my mind. I was on Windows 10 and all was fine.

I upgraded to Windows 11, which was the OS in the above wsl.exe --version output.

Now i've downgraded back to Windows 10 and i'm having the same problem!

I've tried various different versions of WSL Kernel and WSL version. All broken.

WSL version: 1.2.3.0
Kernel version: 5.15.90.1
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.2846

I have compared that with an adjacent PC with a similar spec, where WSL2 is working fine - the versions are all the same.

[TechnoTaff]

I have fixed this, special thanks to @kunzjacq in this thread:

#4926

When I upgraded my PC, I also moved it. I used an ethernet port where once there was a switch. It was set up as a trunked port. If VLANs are present on your ethernet, you get exactly the problem described above.

I have made the port an access port and now everything is fine.

[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!