From owner-freebsd-current@FreeBSD.ORG Sun Nov 4 14:12:15 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 116B62AD; Sun, 4 Nov 2012 14:12:15 +0000 (UTC) (envelope-from null@pozo.com) Received: from pozo.com (pozo.com [216.101.162.50]) by mx1.freebsd.org (Postfix) with ESMTP id 916E98FC0A; Sun, 4 Nov 2012 14:12:14 +0000 (UTC) Received: from T61p.pozo.com (t61p.pozo.com [192.168.0.4]) (authenticated bits=0) by pozo.com (8.14.5/8.14.5) with ESMTP id qA4EBtab006509 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NOT); Sun, 4 Nov 2012 06:11:56 -0800 (PST) (envelope-from null@pozo.com) Message-Id: <201211041411.qA4EBtab006509@pozo.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Sun, 04 Nov 2012 06:11:50 -0800 To: Dimitry Andric From: Manfred Antar Subject: Re: weird network problems on current since 10/28/2012 In-Reply-To: <50964FBB.4010600@andric.com> References: <201211031740.qA3HeqVX001622@pozo.com> <201211040113.qA41DfLn001577@pozo.com> <50964FBB.4010600@andric.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Status: No, score=-0.9 required=5.0 tests=ALL_TRUSTED,MISSING_MID autolearn=no version=3.3.2, No X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on pozo.com X-pozocom-MailScanner-Information: Please contact the ISP for more information X-pozocom-MailScanner-ID: qA4EBtab006509 X-pozocom-MailScanner: Found to be clean X-pozocom-MailScanner-From: null@pozo.com Cc: Adrian Chadd , freebsd-current@freebsd.org, Andre Oppermann X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Nov 2012 14:12:15 -0000 At 03:21 AM 11/4/2012, Dimitry Andric wrote: >On 2012-11-04 02:13, Manfred Antar wrote: >>At 03:29 PM 11/3/2012, Adrian Chadd wrote: >>>On 3 November 2012 10:40, Manfred Antar wrote: >>>>i have problem connecting to freebsd box on local network since last sunday. >>>>the last kernel that works: >>>> FreeBSD 10.0-CURRENT #0: Sun Oct 28 12:14:38 PDT 2012 >>>>anything after that, sometimes i can connect, other times just hangs. >>>>any network connection hangs ===== pop httpd ssh etc etc. >>>>anyone have any ideas ? >>>>i can checkout different sources and see if i can locate the changes that cause this. >>> >>>Please do! >... >>Here is what I found doing : >>setenv CVSROOT /usr/home/ncvs >> >>cvs co -D"October 28, 2012 12:14:38 PDT" sys >> >>A kernel from that time works fine. >> >>doing: >> >>cvs up -D"October 28, 2012 13:14:38 PDT" sys 1 hour later >>the following files were changed: >>sys/netinet/tcp_input.c >>sys/netinet/tcp_timer.c >>sys/netinet/tcp_var.h >> >>Building a kernel from these new files is when the problem starts. > >So, your problems seem to have been introduced by this commit by Andre: > > http://svn.freebsd.org/changeset/base/242266 > > Increase the initial CWND to 10 segments as defined in IETF TCPM > draft-ietf-tcpm-initcwnd-05. It explains why the increased initial > window improves the overall performance of many web services without > risking congestion collapse. > > As long as it remains a draft it is placed under a sysctl marking it > as experimental: > net.inet.tcp.experimental.initcwnd10 = 1 > When it becomes an official RFC soon the sysctl will be changed to > the RFC number and moved to net.inet.tcp. > > This implementation differs from the RFC draft in that it is a bit > more conservative in the case of packet loss on SYN or SYN|ACK because > we haven't reduced the default RTO to 1 second yet. Also the restart > window isn't yet increased as allowed. Both will be adjusted with > upcoming changes. > > Is is enabled by default. In Linux it is enabled since kernel 3.0. > >After the commit, there was a small discussion thread on svn-src-head@ >about the possible problems with the approach. Maybe you are >experiencing those? > >As the commit message says, you should be able to turn the feature off >using: > > sysctl net.inet.tcp.experimental.initcwnd10=0 > >Can you please try that, and see if the problems go away? I read the commit log and tried that. It didn't change. I will try the patch from Andre and enable the debug log. Manfred ======================== || null@pozo.com || || Ph. (415) 681-6235 || ======================== -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.