Many packets with DF set have bad cksums on enc0
-
i see a lot of bad checksums on enc0. Is this normal?
The difference to the right checksum is alway 0x100.
And DF is always set.tcpdump -vvv -i enc0
20:51:36.221753 (authentic,confidential): SPI 0x530d840c: IP (tos 0x0, ttl 126, id 28281, offset 0, flags [DF], proto TCP (6), length 40, bad cksum 9f11 (->a011)!)
10.19.1.150.64621 > 192.168.33.244.80: Flags [.], cksum 0x625a (correct), seq 1, ack 1, win 64766, length 0
20:51:36.221794 (authentic,confidential): SPI 0x530d840c: IP (tos 0x0, ttl 126, id 28282, offset 0, flags [DF], proto TCP (6), length 40, bad cksum 9f10 (->a010)!)
10.19.1.150.64622 > 192.168.33.244.80: Flags [.], cksum 0xfa05 (correct), seq 1, ack 1, win 64766, length 0
20:51:36.222210 (authentic,confidential): SPI 0x530d840c: IP (tos 0x0, ttl 126, id 28283, offset 0, flags [DF], proto TCP (6), length 602, bad cksum 9cdd (->9ddd)!)
10.19.1.150.64621 > 192.168.33.244.80: Flags [P.], seq 1:563, ack 1, win 64766, length 562
20:51:36.222392 (authentic,confidential): SPI 0x530d840c: IP (tos 0x0, ttl 126, id 28284, offset 0, flags [DF], proto TCP (6), length 608, bad cksum 9cd6 (->9dd6)!)
10.19.1.150.64622 > 192.168.33.244.80: Flags [P.], seq 1:569, ack 1, win 64766, length 568