From owner-freebsd-current@FreeBSD.ORG Sat May 10 07:10:19 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24A68106566C for ; Sat, 10 May 2008 07:10:19 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id EE82E8FC1E for ; Sat, 10 May 2008 07:10:18 +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 12B06107970; Sat, 10 May 2008 03:10:17 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Sat, 10 May 2008 03:10:17 -0400 X-Sasl-enc: 7SUs9VWTb5x0pGjDcqdkkj5Y6aGal8J/3RCbzvcbKdDl 1210403416 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 ESMTPSA id 7541B298E3; Sat, 10 May 2008 03:10:16 -0400 (EDT) Message-ID: <48254A57.5040603@FreeBSD.org> Date: Sat, 10 May 2008 08:10:15 +0100 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.12 (X11/20080423) MIME-Version: 1.0 To: Julian Elischer References: <4824F1B4.6010302@elischer.org> In-Reply-To: <4824F1B4.6010302@elischer.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: Multiple routing table support commited X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 May 2008 07:10:19 -0000 Julian, Thanks so much for this. Julian Elischer wrote: > I have committed the base of teh Multi-routing-table support. > I am current;y waiting for it to loop back to me before a final > make universe test, but I think it should be ok. > if you do nothing you should not see any difference. I think you well deserve a break after all that effort. I look forward to p4 merge >;-> [I waded into the pf code last week, to write a patch to allow IP Router Alert out by default -- as it breaks IGMP/MLD and thus link-scope/all multicasting. It looks like it wouldn't be too difficult for someone to add a "setfib" tag, however, this can break backwards compatibility with pfsync'ed nodes if pfstate/pfrule are changed.] > This code, backported to 6.3 is running on Ironport appliances > and Cisco/Ironport has graciously allowed it to be given back. Thanks also to them for making this possible. cheers BMS