WSL2 loses networking after resume from hibernate

Windows Version

Microsoft Windows [Version 10.0.26100.3194]

WSL Version

2.3.26.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.167.4-microsoft-standard-WSL2

Distro Version

Ubuntu 24.04

Other Software

Appgate SDP 6.4.1-39256-release
Zscaler 4.3.0.188

Repro Steps

I have a Dell Latitude 7450 with an "Intel Core Ultra 7" cpu, 32Gb ram.
Due to concerns about mis-interactions on resume with USB3 docking stations, $work has disabled sleep in the bios, leaving only hibernate.

I have noticed that after resume from hibernate my WSL2 vm is unable to make use of any network-related functionality - routing and DNS at a minimum.

The consistent misbehaviour is that I lose the ability to resolve DNS - and I cannot get any ICMP Reply packets when I ping lo or ping loopback0.

Sometimes after resume I can see traffic on the eth? interfaces - including both ICMP Request and Reply - but something is blocking the return path inside the VM for every packet. Other times I cannot see any traffic on the interfaces. I can also see that routes are getting updated but no traffic passes.

I've tried restarting systemd-networkd and systemd-resolved, setting the links down and then up, and even tried manually adding routes. Nothing works to get networking back.

I noticed this morning that running reboot in the VM does not bring the stack back up, I have to use shutdown -h.

Expected Behavior

I expect networking to "just work" after resuming from hibernation

Actual Behavior

WslLogs-2025-03-27_10-05-36.zip

Diagnostic Logs

pcaps.zip

Start by reviewing WslLogs-2025-03-27_10-05-36.zip and pcaps.zip, focusing on the networking state before and after hibernate resume. Trace the resume and shutdown behavior to identify why DNS, routing, and ICMP fail, then verify that networking recovers after hibernate without requiring a full VM shutdown.