From: Wesley Eddy (firstname.lastname@example.org)
Date: Tue, 28 Sep 2004 10:39:21 -0400 From: Wesley Eddy <email@example.com> Subject: Re: tcptrace-bugs Using tcptrace with ns traces Message-ID: <20040928143921.GF22315@grc.nasa.gov>
On Tue, Sep 28, 2004 at 03:56:44PM +0530, Bharath Bhushan wrote:
> 2) The final statistics shows lots of duplicates. When I looked at the
> pread_ns_fulltcp() function, it doesn't seem t care about the
> different kinds of events happening on a packet. So the
> enque/deque/recv etc are all recognized as duplicate packets. Is there
> a way to overcome this?
You want to apply a filter (using awk or equivalent) to grap only the
relevant events. For example, if you have 3 links in your network, your
trace file might contain all events on all 3 links, so single segments
show up dozens of times. For tcptrace, you want to filter out only the
data segments with sent (+) on the sender's link, and ACKs recieved (r)
in the opposite direction on that link. That gives you a "sender-side"
trace, and should satisfy all of tcptrace's algorithmic assumptions.
This archive was generated by hypermail 2.1.7 : 09/28/04 EDT