General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Simon Leinen <simon.leinen@switch.ch>
Cc: "Shawn Ostermann" <ostermann@cs.ohiou.edu>,
	"Toke Høiland-Jørgensen" <toke@toke.dk>,
	bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Passive RTT measurements [was: Re:  Bufferbloat Paper]
Date: Sat, 19 Jan 2013 00:16:08 +0100	[thread overview]
Message-ID: <20130118231607.GB3419@nuttenaction> (raw)
In-Reply-To: <aar4ljx5x0.fsf@switch.ch>

* Simon Leinen | 2013-01-17 15:03:55 [+0100]:

>I have found that with "tcptrace -Z -lrn", I can extract lots of RTT
>samples and also some per-connection statistics (which are useful but
>not as detailed as I'd like to or as in your paper).  This even works in
>finite time, like a couple minutes per 100Mpacket trace of mostly HTTP
>traffic taken near a popular archive server.  As a bonus, it supports IPv6.

Hey Simon,

some years ago I started to develop a clean and easy expendable python
application similar to tcptrace, called captcp:

http://research.protocollabs.com/captcp/


Probably you should take a look at the source code, here the throughput module:

https://github.com/hgn/captcp/blob/master/captcp.py#L2239


Simple python code, TCP streams are already splitted, the packet is also
already parsed (all IP/TCP values) - you simple have to build your logic
around and hook into pre_process_packet() or process_packet().


Cheers, Hagen


      parent reply	other threads:[~2013-01-18 23:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87r4lvgss4.fsf@toke.dk>
2013-01-09  3:39 ` [Bloat] Bufferbloat Paper Mark Allman
2013-01-09  5:02   ` David Lang
2013-01-18  1:23     ` grenville armitage
2013-01-17 14:03   ` [Bloat] Passive RTT measurements [was: Re: Bufferbloat Paper] Simon Leinen
2013-01-17 14:08     ` Simon Leinen
2013-01-18 23:16     ` Hagen Paul Pfeifer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130118231607.GB3419@nuttenaction \
    --to=hagen@jauu.net \
    --cc=bloat@lists.bufferbloat.net \
    --cc=ostermann@cs.ohiou.edu \
    --cc=simon.leinen@switch.ch \
    --cc=toke@toke.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox