tcptrace-bugs Using tcptrace with ns traces

From: Bharath Bhushan (bharath.bhushan@gmail.com)
Date: 09/28/04


Message-ID: <29683db204092803266c3f2b5d@mail.gmail.com>
Date: Tue, 28 Sep 2004 15:56:44 +0530
From: Bharath Bhushan <bharath.bhushan@gmail.com>
Subject: tcptrace-bugs Using tcptrace with ns traces

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/28/04 EDT