From owner-freebsd-net@FreeBSD.ORG Sun Aug 10 09:55:41 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 225D14CB for ; Sun, 10 Aug 2014 09:55:41 +0000 (UTC) Received: from gpo1.cc.swin.edu.au (gpo1.cc.swin.edu.au [136.186.1.30]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 91473201A for ; Sun, 10 Aug 2014 09:55:40 +0000 (UTC) Received: from [136.186.229.37] (garmitage.caia.swin.edu.au [136.186.229.37]) by gpo1.cc.swin.edu.au (8.14.3/8.14.3) with ESMTP id s7A9tbnW008910 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 10 Aug 2014 19:55:37 +1000 Message-ID: <53E74199.5040507@swin.edu.au> Date: Sun, 10 Aug 2014 19:55:37 +1000 From: grenville armitage User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121107 Thunderbird/16.0.2 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: A problem on TCP in High RTT Environment. References: <20140809184232.GF83475@funkthat.com> <8AE1AC56-D52F-4F13-AAA3-BB96042B37DD@lurchi.franken.de> <20140809204500.GG83475@funkthat.com> <3F6BC212-4223-4AAC-8668-A27075DC55C2@lurchi.franken.de> <20140810022350.GI83475@funkthat.com> In-Reply-To: <20140810022350.GI83475@funkthat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Aug 2014 09:55:41 -0000 On 08/10/2014 12:23, John-Mark Gurney wrote: [..] > The next thing would be to get a tcpdump, and take a look at the > window size.. Wireshark has lots of neat tools to make this analysis > easy... Another tool that is good is tcptrace.. It can output a > variety of different graphs that will help you track down, and see > what part of the system is the problem... Also, SIFTR (man siftr) can provide detailed insight into the TCP flow's state over time. cheers, gja