Failed to parse logs. Unexpected file: wireshark_trace_icmp.pcapng
The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

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:

• Network packet discrepancy/drop between Windows Host and WSL2 (#10989), similarity score: 0.74

Closed similar issues:

• WSL2: Do not recieve UDP packets from network interface using mirrored option (#11027), similarity score: 0.77
• Networking mirrored can't work on WSL2 (#10632), similarity score: 0.75
• ping breaks when using experimental.networkingMode=mirrored and a VPN (#10805), similarity score: 0.73
• IP protocol traffic not registering on WSL2 network interface (#6831), similarity score: 0.73

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

Found no WSL traces in the logs

from wsl.

@PeaceZhang doesn't seem related to mirrored networking mode. Same behavior is observed on Windows 10, which doesn't support WSL mirrored mode. It's a name resolution issue. Try pinging using the IP of baidu.com (110.242.68.66) and your trace will show no ICMP errors.

from wsl.

I tried directly ping ip number as your suggestion, but the error still exist:

from wsl.

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

from wsl.