Date: Tue, 23 Dec 2003 00:12:59 -0500 From: Barney Wolff <barney@databus.com> To: Mike Silbersack <silby@silby.com> Cc: net@freebsd.org Subject: Re: Controlling ports used by natd Message-ID: <20031223051259.GA36331@pit.databus.com> In-Reply-To: <20031222182913.M2799@odysseus.silby.com> References: <200312120312.UAA10720@lariat.org> <20031212074519.GA23452@pit.databus.com> <6.0.0.22.2.20031212011133.047ae798@localhost> <20031212083522.GA24267@pit.databus.com> <6.0.0.22.2.20031212103142.04611738@localhost> <20031212181944.GA33245@pit.databus.com> <6.0.0.22.2.20031212161250.045e9408@localhost> <20031213001913.GA40544@pit.databus.com> <6.0.0.22.2.20031212175801.04b066d8@localhost> <20031222182913.M2799@odysseus.silby.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Dec 22, 2003 at 06:33:31PM -0600, Mike Silbersack wrote: > > On Fri, 12 Dec 2003, Brett Glass wrote: > > > 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. It is odd that libalias picks a port number, and then, if the "use sockets" option is set, tries to open a socket on that port. Perhaps if the above option is set, it should bind port 0 and use the port the kernel assigns. If folks think that's a good idea, I could produce a patch to alias_db.c for evaluation. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031223051259.GA36331>