github-actions[bot]
commented
3 weeks ago View similar issues
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!
Open similar issues:
- WSL mirrored network Docker container cannot access Windows service (#10926), similarity score: 0.76
- Mirrored networking IPv6 localhost (and localhost addresses) and hostAddressLoopback (for assigned addresses) not working from host (WSL2) (#10803), similarity score: 0.75
- WSL network crash under constant load (#10817), similarity score: 0.75
- Mirrored networking fine at first but drops after only a few minutes (#11369), similarity score: 0.75
Closed similar issues:
- DNS works however pinging/other traffic does not (#7031), similarity score: 0.77
Note: You can give me feedback by thumbs upping or thumbs downing this comment.
Multiple log files found, using: https://github.com/user-attachments/files/15751492/WslLogs-2024-06-09_12-20-00.2.zip
appxpackage.txt not found
optional-components.txt not found
Error while parsing the logs. See action page for details
withinboredom
chanpreetdhanjal
dcasota
Windows Version
Microsoft Windows [Version 10.0.22631.3672]
WSL Version
WSL version: 2.1.5.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.146.1-2
Distro Version
Ubuntu 24.04
Other Software
Repro Steps
I've tried nearly everything to get mirrored networking mode working again, but for some reason it has stopped working correctly in the last week.
At first, it was similar to other reported issues where mirrored mode would work for about 10-15 minutes and then mysteriously fail. Eventually, it just stopped working altogether. At least that is what I thought. (#11369)
I am still able to ping and I see responses. However, UDP and TCP packets leave the interface, but I never see them return in WSL (though I see their responses and retransmissions in wireshark on the windows side).
I then went on an adventure to uninstall/reinstall network adapters, WSL, etc. None of these things seemed to resolve my issue. It wasn't until I stumbled upon #10842 that I got a crazy idea. My simple idea was to manually set the source port of curl and then use the
iperftrick to see if that was a related issue.To my surprise, this worked exactly once:
curl -v google.com --local-port 12345producing the expected output! When I ran it again, I got:curl: (45) bind failed with errno 98: Address already in usewhich is weird because there is no longer any process listening on that port. Changing the source port does, in fact, cause it to work exactly once, yet again.This leads me to believe that this might be a kernel issue, or some other software doing something weird. So, I go to disable systemd ... and lo-and-behold, things work again!
I do note that specifying the source port via curl still only works exactly once and I don't see it in
ssoutput, which is a bit unusual.I'm kinda stumped at the moment with what systemd might be doing, so any tips would be very much appreciated.
Note that #11143 appears to potentially be a duplicate.
Expected Behavior
Networking to work.
Actual Behavior
Networking does not work.
Diagnostic Logs
Steps followed:
wsl --shutdown.\collect-wsl-logs.ps1curl -v 1.1.1.1(DNS works via tunneling but lets remove as many variables as possible)curl -v 1.1.1.1 --local-port 12345curl -v 1.1.1.1 --local-port 12345WSL startup with systemd: WslLogs-2024-06-09_12-20-00 (2).zip
WSL startup without systemd: WslLogs-2024-06-09_12-27-08 (2).zip