Date: Mon, 22 Dec 2003 22:25:43 -0700 From: Brett Glass <brett@lariat.org> To: Barney Wolff <barney@databus.com>, Mike Silbersack <silby@silby.com> Cc: net@freebsd.org Subject: Re: Controlling ports used by natd Message-ID: <6.0.0.22.2.20031222222449.03cd58c8@localhost> In-Reply-To: <20031223051259.GA36331@pit.databus.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> <20031223051259.GA36331@pit.databus.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 10:12 PM 12/22/2003, Barney Wolff wrote: >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. Good idea. One might also want to set a separate pair of sysctl variables to control the range of ports selected by libalias, just in case the administrator wanted to reserve distinct ports for NAT. --Brett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.0.0.22.2.20031222222449.03cd58c8>