From owner-freebsd-net@FreeBSD.ORG Tue Feb 19 14:02:51 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91D5416A419 for ; Tue, 19 Feb 2008 14:02:51 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by mx1.freebsd.org (Postfix) with ESMTP id 6359013C4E3 for ; Tue, 19 Feb 2008 14:02:51 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 0726F918B9; Tue, 19 Feb 2008 09:02:51 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 19 Feb 2008 09:02:51 -0500 X-Sasl-enc: DW5Lmcw8yyzZ0i0b8qqVYSZeGRui6E07oClvlk2wAPrY 1203429770 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 674E815289; Tue, 19 Feb 2008 09:02:50 -0500 (EST) Message-ID: <47BAE189.2090700@FreeBSD.org> Date: Tue, 19 Feb 2008 14:02:49 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.9 (X11/20080207) MIME-Version: 1.0 To: Tom Judge References: <38548.1203371750@thrush.ravenbrook.com> <47BA010E.3060606@tomjudge.com> In-Reply-To: <47BA010E.3060606@tomjudge.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Nick Barnes , freebsd-net@freebsd.org, Bill Moran Subject: Re: Multiple default routes on multihome host X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Feb 2008 14:02:51 -0000 Tom Judge wrote: > > However FreeBSD's routing table does not currently support policy > routing without some help from the firewall. The only way to achieve > your goal is to use one of the firewalls (pf/ipfw/ipf) to do the > policy routing for you. If anyone wants to take this on, start looking at inpcb, bind, and ip_output(), and try to bug me for help -- "human resources", tcaahh.... I'm getting old :-) later BMS