Date: Sun, 10 Aug 2014 19:55:37 +1000 From: grenville armitage <garmitage@swin.edu.au> To: freebsd-net@freebsd.org Subject: Re: A problem on TCP in High RTT Environment. Message-ID: <53E74199.5040507@swin.edu.au> In-Reply-To: <20140810022350.GI83475@funkthat.com> References: <CAOENNMA_CiBDJc0kchzUbTcf_JBwTJPF=PdBAUB6FPo-KzYkeQ@mail.gmail.com> <20140809184232.GF83475@funkthat.com> <8AE1AC56-D52F-4F13-AAA3-BB96042B37DD@lurchi.franken.de> <20140809204500.GG83475@funkthat.com> <3F6BC212-4223-4AAC-8668-A27075DC55C2@lurchi.franken.de> <CAOENNMCPuiYS7LHwMfOczhZ4yisjGkpOmWzv2pcAoi9Hhzb7dw@mail.gmail.com> <20140810022350.GI83475@funkthat.com>
index | next in thread | previous in thread | raw e-mail
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, gjahome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53E74199.5040507>