From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from g6t1524.atlanta.hp.com (g6t1524.atlanta.hp.com [15.193.200.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "smtp.hp.com", Issuer "VeriSign Class 3 Secure Server CA - G3" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 653EE21F386; Fri, 12 Sep 2014 08:25:02 -0700 (PDT) Received: from g5t1633.atlanta.hp.com (g5t1633.atlanta.hp.com [16.201.144.132]) by g6t1524.atlanta.hp.com (Postfix) with ESMTP id ED14E149; Fri, 12 Sep 2014 15:25:00 +0000 (UTC) Received: from [16.103.148.51] (tardy.usa.hp.com [16.103.148.51]) by g5t1633.atlanta.hp.com (Postfix) with ESMTP id 38C2662; Fri, 12 Sep 2014 15:24:59 +0000 (UTC) Message-ID: <5413104A.4070104@hp.com> Date: Fri, 12 Sep 2014 08:24:58 -0700 From: Rick Jones User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Rich Brown , Jonathan Morton References: <1410482143.8059509@apps.rackspace.com> <45F70DEB-F0FE-45EA-8D27-EEF7C523476B@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Wes Felter , =?UTF-8?B?Sm9lbCBXaXLEgW11IFBhdWxpbmc=?= , "cerowrt-devel@lists.bufferbloat.net" , bloat Subject: Re: [Cerowrt-devel] [Bloat] Fixing bufferbloat: How about an open letter to the web benchmarkers? 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: Fri, 12 Sep 2014 15:25:31 -0000 On 09/11/2014 06:48 PM, Rich Brown wrote: > Jonathan, > >> Could we make use of the existing test servers (running netperf) for that demonstration? How hard is the protocol to fake in Javascript? > > Not having coded a stitch of this, I *think* it would require the following: > > - Web page on netperf-xxx.bufferbloat.net that served out the javascript (required to get around cross-domain protections within the browser) > > - Javascript function to connect back to that host on port 12865 and fake out the netserver with TCP_STREAM or TCP_MAERTS request > > - Javascript that's efficient enough to source/swallow full-rate data stream > > - Cloning the code from https://github.com/apenwarr/blip to make fake pings from TCP requests > > Anyone know more than I do about this? Not about the javascript stuff, but your high level description of the netperf side sounds plausible. There are a few control messages netperf will exchange with netserver that if you want to leverage a remote netserver will need to be included. You can run a netperf command with a higher debug level to see them. rick jones