From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from g9t5008.houston.hp.com (g9t5008.houston.hp.com [15.240.92.66]) (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 C57C821F259 for ; Tue, 21 Apr 2015 09:07:16 -0700 (PDT) Received: from g9t2301.houston.hp.com (g9t2301.houston.hp.com [16.216.185.78]) by g9t5008.houston.hp.com (Postfix) with ESMTP id 1763AAD; Tue, 21 Apr 2015 16:07:12 +0000 (UTC) Received: from [16.103.148.51] (tardy.usa.hp.com [16.103.148.51]) by g9t2301.houston.hp.com (Postfix) with ESMTP id 4097055A; Tue, 21 Apr 2015 16:07:11 +0000 (UTC) Message-ID: <553675AE.2090200@hp.com> Date: Tue, 21 Apr 2015 09:07:10 -0700 From: Rick Jones User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: =?windows-1252?Q?Toke_H=F8iland-J=F8rgensen?= , sahil grover References: <87sibz53kz.fsf@toke.dk> <55313402.5030503@hp.com> <87twwdlias.fsf@toke.dk> <87vbgqizwc.fsf@toke.dk> <87383trh7w.fsf@toke.dk> <87pp6xpq1t.fsf@toke.dk> In-Reply-To: <87pp6xpq1t.fsf@toke.dk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Cc: "codel@lists.bufferbloat.net" Subject: Re: [Codel] RRUL Test X-BeenThere: codel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: CoDel AQM discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Apr 2015 16:07:45 -0000 On 04/21/2015 06:30 AM, Toke Høiland-Jørgensen wrote: > Right, so there's definitely something messing with the outgoing > traffic. I have no idea what could cause netperf to only be able to send > traffic in one direction (perhaps Rick knows?). Do you have any sort of > firewall between you and the internet that might interfere with traffic? Firewall is the first thing that comes to mind. Second would be some sort of PathMTU discovery black-hole. One way to check for that would be to run a TCP_RR test and see if that "works." If it gets a non-zero result, it suggests an issue with large segments (the netperf default request and response size being one byte...). If it gets a zero result, it suggests something else like perhaps firewall. rick jones