From: Bharath Bhushan (email@example.com)
Message-ID: <firstname.lastname@example.org> Date: Wed, 29 Sep 2004 09:44:06 +0530 From: Bharath Bhushan <email@example.com> Subject: Re: tcptrace-bugs Using tcptrace with ns traces
Actually I am using the FullTcp Agent in ns. I am running a simple
fulltcp based simulation (tcl file attached with this mail along with
the trace file). I have not modified ns source code.
About the flags that you mention for proper processing of ns traces, I
assume they are tcptrace compilation flags. Am I right here?
ns version I am using - 2.27
The traces that I have are the "normal traces" with 14 fields (18 for
tcp specific traces). I have not worked with the ns "new" traces.
After applying the patch related to the trace file format recognition
(sent by Joshua Blanton), the ns trace files are getting recognized
properly but lots of hardware duplicates are seen in the tcptrace
Thanks a lot
On Tue, 28 Sep 2004 09:50:35 -0400 (EDT), Angelos Stavrou
> Hi Bharath,
> Can you please send me more information on the ns code you are testing?
> I remember that there are some flags that you need to use for the ns
> traces to be processed properly by tcptrace.
> Also, last time I checked, tcptrace supports ns2 traces - what is
> the version of ns you are using?
> On Tue, 28 Sep 2004, Bharath Bhushan wrote:
> > Hi all,
> > 1) When the two endpoints are 0.0 and 3.0, the tcp connection between
> > them is being recongnized as two separate half-duplex connections. If
> > I change the endpoint addresses to (0.0, 3.1) or (0.1, 3.0), it is
> > recognized as one complete connection. What could the problem be?
> > 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?
> > Thanks in advance
> > -- Bharath
This archive was generated by hypermail 2.1.7 : 09/29/04 EDT