Message-Id: <200303262139.QAA25829@lawyers.ir.bbn.com> From: Mark Allman <mallman@grc.nasa.gov> Subject: Re: tcptrace Slow Start Duration Date: Wed, 26 Mar 2003 16:39:37 -0500
> >From my experience in wireless networks the case that most
> frequently = happens is "window-limited" and that is also the only
> one I would be = interested in. Losses tend not to occur as
> buffering is used at the = border between wired and wireless, the
> other 2 also would not be = relevant to answer the question "for
> how long the bandwidth is = under-utilised".
If you end up being window limited then you cannot answer the
question you have posed because the window is likely limiting the
amount of bandwidth you can attain. For TCP you need to see when
you experience loss to detect when you have hit the upper bound of
the network capacity. (That is a bit wrong in the case of deep
queues, but basically right.)
It sounds like you should be able to get what you are looking for by
writing a quick awk or perl script and then "tcpdump -r file
|script".
allman
-- Mark Allman -- NASA GRC/BBN -- http://roland.grc.nasa.gov/~mallman/ ---------------------------------------------------------------------------- To unsubscribe, send a message with body containing "unsubscribe tcptrace" to majordomo@tcptrace.org.
This archive was generated by hypermail 2b30 : 03/27/03 EST