Fancy bug. about packetnet HOT 3 CLOSED

I think that packet in the pcap file is wrong, the TCP of that packet checksum is also incorrect.

from packetnet.

@Phyxion that's my suspect too, but I also think that it's something that can be addressed directly within the packet dissector inside the library.
At the end of the day Wireshark parse it without many problems.
Am I wrong?
I say so in terms of having a more resilient library. The problem can reside in the PCAP or in TCP/IP stack implementation within one of the appliance in of the test or because it's a forged packet from an "unknown player" (according to the test can be a hacker).
That's are just my two cents, simply can be a good test for the "strongness" of the library have "malformed" packets like that.

from packetnet.

Hi @Anandir. It looks like you've identified an issue with the library. If you would be willing to submit a PR to add a test and a fix that would be great. I'm not sure any of the other developers will have a chance to fix it without your help. Closing this one out as it has been inactive for a while.

from packetnet.