From owner-freebsd-net@FreeBSD.ORG Fri Dec 12 05:26:31 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 0FD0116A4CE for ; Fri, 12 Dec 2003 05:26:31 -0800 (PST) Received: from gw.celabo.org (gw.celabo.org [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id D348043D1D for ; Fri, 12 Dec 2003 05:26:29 -0800 (PST) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (verified OK)) by gw.celabo.org (Postfix) with ESMTP id 67B8A5482B; Fri, 12 Dec 2003 07:26:29 -0600 (CST) Received: by madman.celabo.org (Postfix, from userid 1001) id EF9E46D45F; Fri, 12 Dec 2003 07:26:28 -0600 (CST) Date: Fri, 12 Dec 2003 07:26:28 -0600 From: "Jacques A. Vidrine" To: Brett Glass Message-ID: <20031212132628.GB19204@madman.celabo.org> References: <200312120312.UAA10720@lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200312120312.UAA10720@lariat.org> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.4i-ja.1 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: Fri, 12 Dec 2003 13:26:31 -0000 On Thu, Dec 11, 2003 at 08:12:49PM -0700, Brett Glass wrote: > Is there a way to control the range of ports to which FreeBSD's > natd maps outgoing connections? I'm attempting to deal with a > situation in which natd is (sometimes) changing outgoing UDP > packets' source port numbers to ones which are commonly used > by worms. Sometimes, a firewall at the destination blocks the > packet; at other times, the response is blocked on the way > back. > > If it is possible to tell natd to avoid using ports that are > firewalled, it ought to be possible to avoid this problem. But > I can find no way to do this. Does one exist? I suppose there is brute force. Use an application like PortSentry to bind the ports that you don't want to be used by natd. Cheers, -- Jacques Vidrine NTT/Verio SME FreeBSD UNIX Heimdal nectar@celabo.org jvidrine@verio.net nectar@freebsd.org nectar@kth.se