Checksum: 0x17d1 [incorrect, should be 0x33fc]
This happens with a large variety of packets, PacketAck, StartPingCheck, CompletePingCheck, ect.. The only thing I can tell that might be the culprit is that the packets are not zero padded to a word boundry, which changes the length field in the UDP header, and thus the checksum.
In the end, this could effect the protocols network performance a bit, since either the kernel has to go through and correct the padding, length, and checksum, or something along the way is just gonna drop it as invalid.