tcp packets corruption v0.17+ about packetnet HOT 4 CLOSED

There's very little documentation regarding DRDA packets, but I think the current DRDA implementation (which was added in 0.17) is a very limited way of checking if it's actually a DRDA packet (it's not hard to imagine that another packet arrives with 0xD0 on that position). That said, the data shouldn't get corrupted and you can still access the bytes directly of course.

from packetnet.

I think I've managed to find a fix for this, based on the Wireshark code, I'll submit a PR.

from packetnet.

I've found it when start missing packets after updating dependencies.
May be I'm using Packet.Net in the wrong way?
payload = tcpPacket.PayloadData;

from packetnet.

That's OK, but for performance you might want to use BytesHighPerformance instead. However, there shouldn't be missing packets or data, you can always access the original data. The 'sub' packets are just for parsing only.

I think the PR I've just submitted should fix it though, I don't have any DRDA hits anymore (I used to have them sometimes).

from packetnet.