From owner-freebsd-net@FreeBSD.ORG Thu Aug 7 02:53:12 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 C8B5C37B401 for ; Thu, 7 Aug 2003 02:53:12 -0700 (PDT) Received: from elephant.ru.ac.za (elephant.ru.ac.za [146.231.128.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B31343FA3 for ; Thu, 7 Aug 2003 02:53:06 -0700 (PDT) (envelope-from bvi@lair.moria.org) Received: from segv.ict.ru.ac.za ([146.231.122.34] helo=segv) by elephant.ru.ac.za with smtp (Exim 4.20) id 19khRZ-000Gi4-Lq; Thu, 07 Aug 2003 11:52:25 +0200 Message-ID: <015401c35cc9$9aa65600$227ae792@ict.ru.ac.za> From: "Barry Irwin" To: "Roger 'Rocky' Vetterberg" , "Andre Rein" References: <20030807094647.X77217@juergen.edv-winter.de> <3F3218A2.3040802@401.cx> Date: Thu, 7 Aug 2003 11:52:21 +0200 Organization: Moria Research MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Spam-Score: -1.0 (-) X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/) *19khRZ-000Gi4-Lq*4XiCpes.WOs* cc: freebsd-net@freebsd.org Subject: Re: Firewall with RFC1918 transfer network 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: Thu, 07 Aug 2003 09:53:13 -0000 > >Is there any way to tell her that she have to use her oip 195.226.65.125 > >from fxp1? > > > >greetings > > > >Andre Rein > > > > > > > Set your default route to something that is not in the 192.168.x.x range. > The system automatically uses the interface from which it can reach the > default gateway as its "primary" interface. > AS to solutions you could try the following: 1 - set up NAT on the firewall to re-write outgoing traffic NOT destined for the private network, or your other internal nets 2- possibly set up NAT on the router for the specific FW IP, this would really only affect outgoing traffic, as I understand all the incoming traffic is routed to the FW's 192.168 IP ? Barry -- Barry Irwin bvi@moria.org