From owner-freebsd-net@FreeBSD.ORG Thu Jun 23 07:52:24 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 3F7D616A41C for ; Thu, 23 Jun 2005 07:52:24 +0000 (GMT) (envelope-from ari@suutari.iki.fi) Received: from espresso2.syncrontech.com (sync-old.syncrontech.com [213.28.98.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FFCE43D55 for ; Thu, 23 Jun 2005 07:52:20 +0000 (GMT) (envelope-from ari@suutari.iki.fi) Received: from guinness.syncrontech.com (guinness.syncrontech.com [62.71.8.57]) by espresso2.syncrontech.com (8.12.11/8.12.11) with ESMTP id j5N7qC1j006663; Thu, 23 Jun 2005 10:52:12 +0300 (EEST) (envelope-from ari@suutari.iki.fi) Received: from [62.71.8.37] (coffee.syncrontech.com [62.71.8.37]) by guinness.syncrontech.com (8.12.11/8.12.11) with ESMTP id j5N7q7qi025510; Thu, 23 Jun 2005 10:52:07 +0300 (EEST) (envelope-from ari@suutari.iki.fi) Message-ID: <42BA6A22.6030506@suutari.iki.fi> Date: Thu, 23 Jun 2005 10:52:02 +0300 From: Ari Suutari User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ari Suutari References: <42B7B352.8040806@suutari.iki.fi> In-Reply-To: <42B7B352.8040806@suutari.iki.fi> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Policy routing idea (Was: ipfw: Would it be possible to continue processing rest of rules after match ?) 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: Thu, 23 Jun 2005 07:52:24 -0000 Hi, The patches which implement both "ipfw setnexthop" and "ipfw .... defaultroute" are at: http://www.suutari.iki.fi/freebsd/ipfw-nexthop.patch http://www.suutari.iki.fi/freebsd/netinet-nexthop.patch These are against 5.4-RELEASE - if that causes too much trouble I can try to generate them against -current. I have tested these in lab environment, but not in production use. However, I woudn't expect much problems, since these features use much existing code. Ari S.