From owner-freebsd-questions@FreeBSD.ORG Wed Mar 14 20:51:22 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 35EF716A402 for ; Wed, 14 Mar 2007 20:51:22 +0000 (UTC) (envelope-from wojtek@tensor.gdynia.pl) Received: from chylonia.3miasto.net (chylonia.3miasto.net [83.12.228.78]) by mx1.freebsd.org (Postfix) with ESMTP id 917E813C448 for ; Wed, 14 Mar 2007 20:51:21 +0000 (UTC) (envelope-from wojtek@tensor.gdynia.pl) Received: from chylonia.3miasto.net (localhost [127.0.0.1]) by chylonia.3miasto.net (8.13.8/8.13.4) with ESMTP id l2EKpL8g029548; Wed, 14 Mar 2007 21:51:21 +0100 (CET) (envelope-from wojtek@tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by chylonia.3miasto.net (8.13.8/8.13.4/Submit) with ESMTP id l2EKpLOG029543; Wed, 14 Mar 2007 21:51:21 +0100 (CET) (envelope-from wojtek@tensor.gdynia.pl) X-Authentication-Warning: chylonia.3miasto.net: wojtek owned process doing -bs Date: Wed, 14 Mar 2007 21:51:21 +0100 (CET) From: Wojciech Puchar X-X-Sender: wojtek@chylonia.3miasto.net To: Alexandre Biancalana In-Reply-To: <8e10486b0703141250i5e016058pbc5f6370144fa5c1@mail.gmail.com> Message-ID: <20070314215033.E29424@chylonia.3miasto.net> References: <0A8464C8-EC5B-4276-8EDC-E5348F99806D@messier.com> <8e10486b0703141250i5e016058pbc5f6370144fa5c1@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-questions@freebsd.org Subject: Re: per-interface default routes? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Mar 2007 20:51:22 -0000 >> I'm likely to do the ipfw approach suggested by Wojceich, >> as soon as I rebuild with "options IPFIREWALL_FORWARD", > > > This could be done with pf route-to too. yes. but ipfw is most universal having all needed things at one place. firewalling, routing, shaping, etc.