From owner-freebsd-net@FreeBSD.ORG Tue Jun 1 16:12:22 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 5117316A4D1 for ; Tue, 1 Jun 2004 16:12:22 -0700 (PDT) Received: from mtaw4.prodigy.net (mtaw4.prodigy.net [64.164.98.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01B9C43D5E for ; Tue, 1 Jun 2004 16:12:22 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (2acd0ca818ef5c01d4c3684f36793205@adsl-67-115-73-128.dsl.lsan03.pacbell.net [67.115.73.128]) by mtaw4.prodigy.net (8.12.10/8.12.10) with ESMTP id i51NCDfY019185; Tue, 1 Jun 2004 16:12:14 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 7196052364; Tue, 1 Jun 2004 16:12:13 -0700 (PDT) Date: Tue, 1 Jun 2004 16:12:13 -0700 From: Kris Kennaway To: Mike Silbersack Message-ID: <20040601231213.GA3894@xor.obsecurity.org> References: <20040601120238.B44353@atlantis.atlantis.dp.ua> <20040601120412.B63021@odysseus.silby.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bp/iNruPH9dso1Pn" Content-Disposition: inline In-Reply-To: <20040601120412.B63021@odysseus.silby.com> User-Agent: Mutt/1.4.2.1i 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: Tue, 01 Jun 2004 23:12:22 -0000 --bp/iNruPH9dso1Pn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 01, 2004 at 12:05:35PM -0500, Mike Silbersack wrote: >=20 > On Tue, 1 Jun 2004, Dmitry Pryanishnikov wrote: >=20 > > The main question is: how to prevent this situation? Of course, as a > > workaround I can set net.inet.ip.portrange.randomized to zero, but what= 's > > the real solution? Is it FTP-client or FTP-server that should take care= of > > the previous DATA port usage? Or even network stack behaviour should be > > further modified to avoid this collision? > > > > Sincerely, Dmitry > > -- > > Atlantis ISP, System Administrator > > e-mail: dmitry@atlantis.dp.ua > > nic-hdl: LYNX-RIPE >=20 > 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 --bp/iNruPH9dso1Pn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAvQ1NWry0BWjoQKURAtggAKCUpLp0V3uhqGflI0KIXS3ag5qTJACePwJc G3NeXTPPcR6Qf4eXvpqAuVM= =D6zy -----END PGP SIGNATURE----- --bp/iNruPH9dso1Pn--