You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've encountered this issue where I can't access the tcp payload data during a live recording with SharpPcap and PacketDotNet.
Looked into it a bit deeper and found out that during live recording the fragmented packets have the wrong length.
Attached is a pcap that I created using the CaptureFileWriterDevice as wireshark didn't produce faulty packets.
pcap.zip
The packet in question:
Image of the packet recorded using wireshark (not the same recording):
Maybe it's because I'm capturing the loopback device? Is this a bug in sharpcap or is it the driver?
Using Windows 10, SharpPcap 6.2.5, Npcap 1.72
Also tried using the CreatingCaptureFile example with the same result.
The text was updated successfully, but these errors were encountered:
I've encountered this issue where I can't access the tcp payload data during a live recording with SharpPcap and PacketDotNet.
Looked into it a bit deeper and found out that during live recording the fragmented packets have the wrong length.
Attached is a pcap that I created using the CaptureFileWriterDevice as wireshark didn't produce faulty packets.
pcap.zip
The packet in question:
Image of the packet recorded using wireshark (not the same recording):
Maybe it's because I'm capturing the loopback device? Is this a bug in sharpcap or is it the driver?
Using Windows 10, SharpPcap 6.2.5, Npcap 1.72
Also tried using the CreatingCaptureFile example with the same result.
The text was updated successfully, but these errors were encountered: