From owner-freebsd-net@FreeBSD.ORG Mon Oct 10 06:52:22 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C1E2016A41F for ; Mon, 10 Oct 2005 06:52:22 +0000 (GMT) (envelope-from on@cs.ait.ac.th) Received: from mail.cs.ait.ac.th (mail.cs.ait.ac.th [192.41.170.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7336143D53 for ; Mon, 10 Oct 2005 06:52:21 +0000 (GMT) (envelope-from on@cs.ait.ac.th) Received: from banyan.cs.ait.ac.th (banyan.cs.ait.ac.th [192.41.170.5]) by mail.cs.ait.ac.th (8.12.11/8.12.11) with ESMTP id j9A6qI2l045011 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 10 Oct 2005 13:52:18 +0700 (ICT) Received: (from on@localhost) by banyan.cs.ait.ac.th (8.13.1/8.12.11) id j9A6qIbV015852; Mon, 10 Oct 2005 13:52:18 +0700 (ICT) Date: Mon, 10 Oct 2005 13:52:18 +0700 (ICT) Message-Id: <200510100652.j9A6qIbV015852@banyan.cs.ait.ac.th> From: Olivier Nicole CC: freebsd-net@freebsd.org In-reply-to: <20051010012831.G60693@odysseus.silby.com> (message from Mike Silbersack on Mon, 10 Oct 2005 01:31:03 -0500 (CDT)) References: <200510100622.j9A6MMbW014091@banyan.cs.ait.ac.th> <20051010012831.G60693@odysseus.silby.com> X-Virus-Scanned: on CSIM by amavisd-milter (http://www.amavis.org/) Subject: Re: SYN limit 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, 10 Oct 2005 06:52:22 -0000 > FreeBSD has no SYN rate limit, but you could be running into TIME_WAIT > recycling issues. I already set tcp.msl to 5000 to release the TIME WAIT quickly. > Run a netstat on both the client and server, see if the port numbers > match. For example, see if the client is trying to connect to port 3549 > and the server has a TIME_WAIT socket on port 3549. The connection is > supposed to recycle, but under certain conditions it might not... I could not find any port conflict. > After doing that, try setting net.inet.ip.portrange.randomized=0 and see > if the problem clears up at all. Tried that too but it dod not help. olivier