From owner-freebsd-net@FreeBSD.ORG Mon Jan 5 13:13:25 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 393CB106566B; Mon, 5 Jan 2009 13:13:25 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 141F78FC19; Mon, 5 Jan 2009 13:13:25 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 9ED7546B2C; Mon, 5 Jan 2009 08:13:24 -0500 (EST) Date: Mon, 5 Jan 2009 13:13:24 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Lin Jui-Nan Eric In-Reply-To: <47713ee10901012249w65c659bbp3366e4d8ef25c59d@mail.gmail.com> Message-ID: References: <47713ee10812301206j12b35264o715976c154080a1b@mail.gmail.com> <47713ee10901012147k1f25c31bn512dd29b2b294ad5@mail.gmail.com> <47713ee10901012249w65c659bbp3366e4d8ef25c59d@mail.gmail.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, stable@freebsd.org Subject: Re: TCP packet out-of-order problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jan 2009 13:13:25 -0000 On Fri, 2 Jan 2009, Lin Jui-Nan Eric wrote: > After running "netstat -s -p tcp", we found that lots of packets are > discarded due to memory problems. We googled for it, and found that sysctl > oid "net.inet.tcp.reass.maxsegments" became 0, therefore packets never > reassembled. > > Then we checked our /boot/loader.conf and /etc/sysctl.conf, and found that > setting kern.ipc.nmbclusters="0" makes net.inet.tcp.reass.maxsegments=0. > After setting net.inet.tcp.reass.maxsegments="1600" in /boot/loader.conf, > the network works perfectly now. Was it set to 0 through a configuration error, or did the system auto-tune improperly? Robert N M Watson Computer Laboratory University of Cambridge > > Thank you all for the help! > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >