From: Pete Heist <pete@heistp.net>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: ecn-sane@lists.bufferbloat.net
Subject: Re: [Ecn-sane] cctrace prototype
Date: Wed, 20 Mar 2019 11:11:44 +0100 [thread overview]
Message-ID: <226F087E-8A70-4F62-964C-AC2A4B1B0885@heistp.net> (raw)
In-Reply-To: <C3944A2B-211E-460D-AE69-6FE672E98237@heistp.net>
> On Mar 20, 2019, at 8:20 AM, Pete Heist <pete@heistp.net> wrote:
>
> I’ll push what’s available so far later this morning, needs some cleanup…
Code: https://github.com/heistp/cctrace
Updated samples: https://www.heistp.net/downloads/cctrace/
Proportions are calculated now by direction, which also cleaned up some of the output. Also, I now ignore flags for SYN packets.
Probably easiest to use Issues for further requests / bugs…
prev parent reply other threads:[~2019-03-20 10:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D0CB5F2-93DD-4072-81C8-96F8ECAC870D@heistp.net>
2019-03-20 3:42 ` Jonathan Morton
2019-03-20 7:20 ` Pete Heist
2019-03-20 10:11 ` Pete Heist [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/ecn-sane.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=226F087E-8A70-4F62-964C-AC2A4B1B0885@heistp.net \
--to=pete@heistp.net \
--cc=chromatix99@gmail.com \
--cc=ecn-sane@lists.bufferbloat.net \
/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