From owner-freebsd-net@FreeBSD.ORG Fri Aug 8 02:00:45 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 B1B6F37B401 for ; Fri, 8 Aug 2003 02:00:45 -0700 (PDT) Received: from juergen.edv-winter.de (juergen.edv-winter.de [195.226.65.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE72643FDF for ; Fri, 8 Aug 2003 02:00:43 -0700 (PDT) (envelope-from ar@g23.org) Received: from localhost (localhost [127.0.0.1]) by juergen.edv-winter.de (8.12.9/8.12.9) with ESMTP id h77BOYm6088081; Thu, 7 Aug 2003 13:24:34 +0200 (CEST) (envelope-from ar@g23.org) Date: Thu, 7 Aug 2003 13:24:34 +0200 (CEST) From: Andre Rein X-X-Sender: ar@juergen.edv-winter.de To: Barry Irwin In-Reply-To: <015401c35cc9$9aa65600$227ae792@ict.ru.ac.za> Message-ID: <20030807132257.N77217@juergen.edv-winter.de> References: <20030807094647.X77217@juergen.edv-winter.de> <3F3218A2.3040802@401.cx> <015401c35cc9$9aa65600$227ae792@ict.ru.ac.za> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org cc: Roger 'Rocky' Vetterberg Subject: Re: Firewall with RFC1918 transfer network [solved] 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, 08 Aug 2003 09:00:46 -0000 On Thu, 7 Aug 2003, Barry Irwin wrote: > > > >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 > > Thx, problem is solved. Now I'm using NAT at the firewall. greetings Andre Rein -- "And some greetings from the Toaster"