[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ns] Tracing TCP

To: "Nikolaos Katsarakis Austauschstud. (M. Schweigel)" <[email protected]>
Subject: Re: [ns] Tracing TCP
From: Dimitris Velenis <[email protected]>
Date: Sat, 14 Jul 2001 15:17:37 +0300
Cc: ns-users <[email protected]>
In-Reply-To: <[email protected]>; from [email protected] on Fri, Jul 13, 2001 at 09:19:45PM +0200
References: <[email protected]>
Sender: [email protected]
User-Agent: Mutt/1.2i

I suppose you can look in the trace file for 3 (or whatever value you have set
numdupacks_ to) duplicate ACKs requesting the retransmitted segment. If you
find those acks in the trace file then the retransmission was due to Fast Retransmit. 
If not then you had a retransmission timer timout.

Dimitris.

On Fri, Jul 13, 2001 at 09:19:45PM +0200, Nikolaos Katsarakis Austauschstud. (M. Schweigel) wrote:
> Dear ns-users
> 
> Is there any way to distinguish in the ns track file the retransmitions
> due to timeout of retransmission timer of TCP?
> 
> I tried to enable tracing TCP headers, by changing ns-default.tcl and
> recompiling, but I only got zeros in the extra fields. I am using
> one-way TCP, are the TCP headers only useful for FullTCP?
> 
> Thank you very much?
> 
> Nikos

-- 
Dimitris Velenis                              <[email protected]>
Network Management & Optimal Design Lab
National Technical University of Athens

Follow-Ups:
- Re: [ns] Tracing TCP
  - From: "Nikolaos Katsarakis Austauschstud. (M. Schweigel)" <[email protected]>

References:
- [ns] Tracing TCP
  - From: "Nikolaos Katsarakis Austauschstud. (M. Schweigel)" <[email protected]>

Prev by Date: [ns] wireless error model
Next by Date: Re: [ns] Tracing TCP
Prev by thread: [ns] Tracing TCP
Next by thread: Re: [ns] Tracing TCP
Index(es):
- Date
- Thread