From owner-freebsd-net@FreeBSD.ORG Tue Jun 1 17:03:42 2004 Return-Path: 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 8AD9B16A4CE for ; Tue, 1 Jun 2004 17:03:42 -0700 (PDT) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id D699143D58 for ; Tue, 1 Jun 2004 17:03:41 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 69352 invoked from network); 2 Jun 2004 00:03:28 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 2 Jun 2004 00:03:28 -0000 X-pair-Authenticated: 209.68.2.70 Date: Tue, 1 Jun 2004 19:03:27 -0500 (CDT) From: Mike Silbersack To: Kris Kennaway In-Reply-To: <20040601231213.GA3894@xor.obsecurity.org> Message-ID: <20040601185912.I83544@odysseus.silby.com> References: <20040601120238.B44353@atlantis.atlantis.dp.ua> <20040601231213.GA3894@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Dmitry Pryanishnikov cc: freebsd-net@freebsd.org Subject: Re: net.inet.ip.portrange.randomized=1 hurts X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 00:03:42 -0000 On Tue, 1 Jun 2004, Kris Kennaway wrote: > On Tue, Jun 01, 2004 at 12:05:35PM -0500, Mike Silbersack wrote: > > Sounds like something that should be dealt with on the server's end. Some > > of the changes we've made in 5.x might fix the problem, but I don't think > > anyone has looked into that specific case. > > Is this also the cause of the mysql server connection failures > reported on freebsd-stable@? > > Kris Yes, it is possible that random ephemeral port allocation could cause the MySQL problems, if the connection rate is extremely high. If it's happening, it would show up in the form of sockets stuck in the SYN_SENT state. If one of the people reporting problems can verify it, I could backport the changes I made to handle this edgecase in 5.x. Mike "Silby" Silbersack