From: Alan Goodman <notifications@yescomputersolutions.com>
To: Billy Tallis <wtallis@gmail.com>, Sebastian Moeller <moeller0@gmx.de>
Cc: Andy Furniss <adf.lists@gmail.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
"lartc@vger.kernel.org" <lartc@vger.kernel.org>
Subject: Re: [Cerowrt-devel] Correctly calculating overheads on unknown connections
Date: Sun, 21 Sep 2014 22:40:14 +0100 [thread overview]
Message-ID: <541F45BE.9040208@yescomputersolutions.com> (raw)
In-Reply-To: <CAK1m8mPBWyg-sR-ekZGUhsOG-0HoZd3eJ-Q6HJpSLyN-J90kHg@mail.gmail.com>
Hi Billy,
Please can you share your modified script?
Alan
On 21/09/14 22:18, Billy Tallis wrote:
> On my Linux boxes ping has a -A option for adaptive ping, effectively
> sending out a new ping as soon as the reply to the last one is received,
> instead of having to wait a fixed period of time between pings. I
> modified ping_sweeper to use that last December when I was still on a
> DSL link and was able to find the overhead with only a few minutes of
> collecting data. (The connection was 6Mbps down, 512kbps up.) There was
> a bit of noise in the data from other traffic in the house, but the
> stair-step shape of the plot was unmistakeable and the octave script had
> no trouble identifying the per-packet overhead.
next prev parent reply other threads:[~2014-09-21 21:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <541C9527.1070105@yescomputersolutions.com>
[not found] ` <541DA8B5.70701@gmail.com>
2014-09-20 17:55 ` Dave Taht
2014-09-20 22:29 ` Andy Furniss
2014-09-21 18:35 ` Sebastian Moeller
[not found] ` <CAK1m8mPBWyg-sR-ekZGUhsOG-0HoZd3eJ-Q6HJpSLyN-J90kHg@mail.gmail.com>
2014-09-21 21:40 ` Alan Goodman [this message]
2014-09-22 9:05 ` Sebastian Moeller
2014-09-22 10:01 ` Andy Furniss
2014-09-22 10:20 ` Sebastian Moeller
2014-09-22 13:09 ` Alan Goodman
2014-09-22 19:52 ` Sebastian Moeller
2014-09-22 23:02 ` Alan Goodman
2014-09-23 9:32 ` Sebastian Moeller
2014-09-23 15:10 ` Andy Furniss
2014-09-23 17:47 ` Sebastian Moeller
2014-09-23 19:05 ` Andy Furniss
2014-09-23 22:16 ` Sebastian Moeller
2014-09-24 9:17 ` Andy Furniss
2014-09-24 16:23 ` Sebastian Moeller
2014-09-24 22:48 ` Andy Furniss
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=541F45BE.9040208@yescomputersolutions.com \
--to=notifications@yescomputersolutions.com \
--cc=adf.lists@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=lartc@vger.kernel.org \
--cc=moeller0@gmx.de \
--cc=wtallis@gmail.com \
/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