From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.yescomputersolutions.com (mail1.yescomputersolutions.com [84.234.22.193]) by huchra.bufferbloat.net (Postfix) with ESMTP id CD74421F3F2 for ; Sun, 21 Sep 2014 14:40:20 -0700 (PDT) Received: from localhost (unknown [127.0.0.1]) by mail1.yescomputersolutions.com (Postfix) with ESMTP id 625A1380047F; Sun, 21 Sep 2014 21:40:17 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.yescomputersolutions.com Received: from mail1.yescomputersolutions.com ([127.0.0.1]) by localhost (sh1.yescomputersolutions.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h6m_ZkOc_3RC; Sun, 21 Sep 2014 22:40:15 +0100 (BST) Received: from [192.168.25.41] (host81-149-38-69.in-addr.btopenworld.com [81.149.38.69]) by mail1.yescomputersolutions.com (Postfix) with ESMTPSA id 88D95380047D; Sun, 21 Sep 2014 22:40:15 +0100 (BST) Message-ID: <541F45BE.9040208@yescomputersolutions.com> Date: Sun, 21 Sep 2014 22:40:14 +0100 From: Alan Goodman User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Billy Tallis , Sebastian Moeller References: <541C9527.1070105@yescomputersolutions.com> <541DA8B5.70701@gmail.com> <6DF5DFA0-D88E-470E-ACB6-37703EA964E7@gmx.de> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 22 Sep 2014 10:01:39 -0700 Cc: Andy Furniss , "cerowrt-devel@lists.bufferbloat.net" , "lartc@vger.kernel.org" Subject: Re: [Cerowrt-devel] Correctly calculating overheads on unknown connections X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2014 21:40:49 -0000 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.