That version is a bit out of date (3.4.4 is the latest), but I'm not
aware of anything that would change that functionality since 3.4.1.
If you get a chance, give 3.4.4 a try (it does fix other bugs) and
I'll see about reproducing your problem and coming up with a fix in
3.4.5.

-- 
Aaron Turner
http://synfin.net/         Twitter: @synfinatic
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
"carpe diem quam minimum credula postero"




2010/12/16 Виноградов Юрий <[email protected]>:
> I am using tcprewrite version 3.4.1 (build 2229).
>
> -----Original Message-----
> From: Aaron Turner [mailto:[email protected]]
> Sent: Thursday, December 16, 2010 12:42 AM
> To: Main forum for tcpreplay
> Subject: Re: [Tcpreplay-users] tcprewrite: UDP checksum error when 
> fragmenting it
>
> 2010/12/15 Виноградов Юрий <[email protected]>:
>> Hello everyone!
>>
>>
>>
>> I have an error in checksum field in first UDP-fragment, when I try to make
>> fragmentation my one UDP datagram.
>>
>> As I know, the checksum original UDP datagram must be the same as checksum
>> fragmented UDP datagram, but I get different L
>>
>> my script is:
>>
>> tcprewrite --fragroute=frag.cfg --infile=1udp.pcap --outfile=1udp_frag.pcap
>>
>> my frag.cfg contains:
>>
>> ip_frag 1000
>>
>> 1udp.pcap is ~1300 bytes long
>
> Possible bug.  what version of tcprewrite are you using?
>

------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
Tcpreplay-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tcpreplay-users
Support Information: http://tcpreplay.synfin.net/trac/wiki/Support

Reply via email to