From owner-freebsd-questions Sat Feb 16 9: 2:34 2002 Delivered-To: freebsd-questions@freebsd.org Received: from fremont.bolingbroke.com (adsl-216-102-90-210.dsl.snfc21.pacbell.net [216.102.90.210]) by hub.freebsd.org (Postfix) with ESMTP id C2A3F37B400 for ; Sat, 16 Feb 2002 09:02:31 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by fremont.bolingbroke.com (8.12.1/8.12.1) with ESMTP id g1GH2VLA039749; Sat, 16 Feb 2002 09:02:31 -0800 (PST) Date: Sat, 16 Feb 2002 09:02:31 -0800 (PST) From: Ken Bolingbroke X-X-Sender: ken@fremont.bolingbroke.com To: Shawn Dillon Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Natd,ipfw,vnc and multiple interfaces In-Reply-To: <004b01c1b703$21b26990$05e6b38e@lantechhome> Message-ID: <20020216085519.E91586-100000@fremont.bolingbroke.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 16 Feb 2002, Shawn Dillon wrote: > One more question. I remember a post on starting natd and getting a 'unable > to bind divert address" error because natd was already in use. How does this > affect starting multiple natd daemons. > > And thanks for the response thus far. Use the -p option to natd to specify a different port to listen on, and then use that new port in your ipfw rules as well. That is, the respective natd and ipfw rules might look something like: natd -n fxp0 add divert natd all from any to any via fxp0 natd -n fxp1 -p 8669 add divert 8669 all from any to any via fxp1 Ken Bolingbroke hacker@bolingbroke.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message