I had the same behaviour: debian hosts using e1000 driver with a MTU 9000 vlan, dropping 4 bytes on every TCP packet who's size was in the vicinity of 4025: Server side: 14:20:58.899828 IP 1...
See more...
I had the same behaviour: debian hosts using e1000 driver with a MTU 9000 vlan, dropping 4 bytes on every TCP packet who's size was in the vicinity of 4025: Server side: 14:20:58.899828 IP 10.10.22.1.8000 > 10.10.22.21.34222: Flags [P.], seq 27011:31036, ack 184, win 8009, options [nop,nop,TS val 371053137 ecr 2338244542], length 4025 Client side: 14:20:59.196651 IP truncated-ip - 4 bytes missing! 10.10.22.1.8000 > 10.10.22.21.34222: Flags [P.], seq 27011:31036, ack 184, win 8009, options [nop,nop,TS val 371053243 ecr 2338244542], length 4025 I didn't want to switch to vmxnet3 drivers or disable jumbo frames right away, so I went with setting the MTU to 3000 (For the sake of keeping jumbo frames. I'd recommend simply going back to standard MTU 1500, there's not that much to win from it anyway). As fragmented packets now stay below the 4K limit, everything is smooth again, no more truncated packets !