From owner-freebsd-net@FreeBSD.ORG Tue Jun 1 10:05:40 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 73F8016A4CF for ; Tue, 1 Jun 2004 10:05:40 -0700 (PDT) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id DE94E43D46 for ; Tue, 1 Jun 2004 10:05:39 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 79811 invoked from network); 1 Jun 2004 17:05:38 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 1 Jun 2004 17:05:38 -0000 X-pair-Authenticated: 209.68.2.70 Date: Tue, 1 Jun 2004 12:05:35 -0500 (CDT) From: Mike Silbersack To: Dmitry Pryanishnikov In-Reply-To: <20040601120238.B44353@atlantis.atlantis.dp.ua> Message-ID: <20040601120412.B63021@odysseus.silby.com> References: <20040601120238.B44353@atlantis.atlantis.dp.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 17:05:40 -0000 On Tue, 1 Jun 2004, Dmitry Pryanishnikov wrote: > 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 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. A simpler solution might be to use passive mode. I think that you can set that somewhere in the install options. Mike "Silby" Silbersack