Date: Tue, 1 Jun 2004 16:12:13 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Mike Silbersack <silby@silby.com> Cc: freebsd-net@freebsd.org Subject: Re: net.inet.ip.portrange.randomized=1 hurts Message-ID: <20040601231213.GA3894@xor.obsecurity.org> In-Reply-To: <20040601120412.B63021@odysseus.silby.com> References: <20040601120238.B44353@atlantis.atlantis.dp.ua> <20040601120412.B63021@odysseus.silby.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040601231213.GA3894>