From owner-freebsd-net@FreeBSD.ORG Mon Dec 22 16:33:36 2003 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 5D24216A4CE for ; Mon, 22 Dec 2003 16:33:36 -0800 (PST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id D6E4D43D5A for ; Mon, 22 Dec 2003 16:33:34 -0800 (PST) (envelope-from silby@silby.com) Received: (qmail 48523 invoked from network); 23 Dec 2003 00:33:33 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 23 Dec 2003 00:33:33 -0000 X-pair-Authenticated: 209.68.2.70 Date: Mon, 22 Dec 2003 18:33:31 -0600 (CST) From: Mike Silbersack To: Brett Glass In-Reply-To: <6.0.0.22.2.20031212175801.04b066d8@localhost> Message-ID: <20031222182913.M2799@odysseus.silby.com> References: <200312120312.UAA10720@lariat.org> <20031212074519.GA23452@pit.databus.com> <20031212083522.GA24267@pit.databus.com> <20031212181944.GA33245@pit.databus.com> <20031213001913.GA40544@pit.databus.com> <6.0.0.22.2.20031212175801.04b066d8@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Barney Wolff cc: net@freebsd.org Subject: Re: Controlling ports used by natd 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, 23 Dec 2003 00:33:36 -0000 On Fri, 12 Dec 2003, Brett Glass wrote: > net.inet.ip.portrange.lowfirst: 1023 > net.inet.ip.portrange.lowlast: 600 > net.inet.ip.portrange.first: 1024 > net.inet.ip.portrange.last: 5000 > net.inet.ip.portrange.hifirst: 49152 > net.inet.ip.portrange.hilast: 65535 > > Why is "lowfirst" greater than "lowlast" above? That's just an implementation issue, nothing major. The port choosing algorithm can handle both the cases where first > last and last > first, and someone put the low ports in that order. > It is also interesting that natd doesn't respect the > "hifirst..hilast" settings here. Shouldn't it look at > these variables and avoid assigning ports that the > machine on which it's running would not use? Or should > there be a "net.inet.alias.portrange.first", etc., so > that one could specify the ranges or lists for everything > in one place? The high range is really a "feature" added for ftpd's sake, if you take a look back through the cvs history. There's no problem with the normal and high ranges overlapping; -current uses 49152-65535 for both. Mike "Silby" Silbersack