All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Goodman <notifications@yescomputersolutions.com>
To: lartc@vger.kernel.org
Subject: Re: [Cerowrt-devel] Correctly calculating overheads on unknown connections
Date: Sun, 21 Sep 2014 21:40:14 +0000	[thread overview]
Message-ID: <541F45BE.9040208@yescomputersolutions.com> (raw)
In-Reply-To: <6DF5DFA0-D88E-470E-ACB6-37703EA964E7@gmx.de>

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.


  reply	other threads:[~2014-09-21 21:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-21 18:35 [Cerowrt-devel] Correctly calculating overheads on unknown connections Sebastian Moeller
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

* 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=lartc@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.