From owner-freebsd-questions Thu Apr 26 16:56:21 2001 Delivered-To: freebsd-questions@freebsd.org Received: from nameserver.austclear.com.au (nameserver.austclear.com.au [192.83.119.132]) by hub.freebsd.org (Postfix) with ESMTP id E8A3137B422 for ; Thu, 26 Apr 2001 16:56:18 -0700 (PDT) (envelope-from ahl@austclear.com.au) Received: from tungsten.austclear.com.au (tungsten.austclear.com.au [192.168.70.1]) by nameserver.austclear.com.au (8.9.3/8.9.3) with ESMTP id JAA94004; Fri, 27 Apr 2001 09:56:18 +1000 (EST) Received: from tungsten (tungsten [192.168.70.1]) by tungsten.austclear.com.au (8.9.3/8.9.3) with ESMTP id JAA18815; Fri, 27 Apr 2001 09:56:17 +1000 (EST) Message-Id: <200104262356.JAA18815@tungsten.austclear.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: Chris Hardie Cc: questions@FreeBSD.ORG Subject: Re: Confusion about router/firewall traffic from router itself In-Reply-To: Message from Chris Hardie of "Thu, 26 Apr 2001 18:30:23 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Apr 2001 09:56:17 +1000 From: Tony Landells Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Basically I can see two options: 1. Run natd on the external interface so it maps 192.168.21.9 to some registered address (you could even use one from your 208.196.32.193/26 range if you're careful--but I'd probably avoid the one assigned to your internal interface). 2. Configure the various services to use the internal interface as the source address. Most services can do this, but you basically need to do it for each service you care about which could be reasonably time-consuming and error-prone. Cheers, Tony -- Tony Landells Senior Network Engineer Ph: +61 3 9677 9319 Australian Clearing Services Pty Ltd Fax: +61 3 9677 9355 Level 4, Rialto North Tower 525 Collins Street Melbourne VIC 3000 Australia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message