Using too large of a MSS will cause capr-maker to generate frames >
1500 bytes (standard MTU) and generate a "message too long" error, but
using 1260 MSS should be fine.
What is the tcpreplay command which is generating the truncated frame
error? Care to send me the pcap & what version of tcpreplay you are
using?
--
Aaron Turner
http://synfin.net/
http://tcpreplay.synfin.net/ - Pcap editing and replay tools for Unix & Windows
Those who would give up essential Liberty, to purchase a little temporary
Safety, deserve neither Liberty nor Safety.
-- Benjamin Franklin
Ah, now I see.
This is a bug in capr-maker I think. Those errors are generated by
tcpdump (which is used to generate the --verbose output). The reason
for the error is that the IPv6 header says the payload is X bytes, but
the actual payload after the v6 header is 40 bytes smaller then X. My
guess is that capr-maker thinks the IPv6 header is part of the payload
length calculation. :)
I'll mention this to Kowsik when he gets in.
Ah, now I see.
This is a bug in capr-maker I think. Those errors are generated by
tcpdump (which is used to generate the --verbose output). The reason
for the error is that the IPv6 header says the payload is X bytes, but
the actual payload after the v6 header is 40 bytes smaller then X. My
guess is that capr-maker thinks the IPv6 header is part of the payload
length calculation. :)