From owner-freebsd-net@FreeBSD.ORG Tue Feb 22 15:59:20 2005 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 F317D16A4CE for ; Tue, 22 Feb 2005 15:59:19 +0000 (GMT) Received: from eep.lcs.mit.edu (eep.lcs.mit.edu [18.31.0.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82C5F43D31 for ; Tue, 22 Feb 2005 15:59:19 +0000 (GMT) (envelope-from dga@eep.lcs.mit.edu) Received: from eep.lcs.mit.edu (localhost.lcs.mit.edu [127.0.0.1]) by eep.lcs.mit.edu (8.13.1/8.12.9) with ESMTP id j1MFxFgI023758 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Feb 2005 10:59:17 -0500 (EST) (envelope-from dga@eep.lcs.mit.edu) Received: (from dga@localhost) by eep.lcs.mit.edu (8.13.1/8.13.1/Submit) id j1MFxC53023757; Tue, 22 Feb 2005 10:59:12 -0500 (EST) (envelope-from dga) Date: Tue, 22 Feb 2005 10:59:12 -0500 From: "David G. Andersen" To: Andre Oppermann Message-ID: <20050222155912.GA23378@lcs.mit.edu> References: <20050209170802.GA39472@lcs.mit.edu> <420A4957.15E0D656@networx.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <420A4957.15E0D656@networx.ch> User-Agent: Mutt/1.4.2.1i X-Spam-Status: No, hits=-4.9 required=5 tests=BAYES_00 version=FluxMilter1.2 X-Scanned-By: MIMEDefang 2.44 cc: freebsd-net@freebsd.org cc: "David G. Andersen" Subject: Re: Kern/73129 and 5.3-STABLE 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: Tue, 22 Feb 2005 15:59:20 -0000 On Wed, Feb 09, 2005 at 06:33:11PM +0100, Andre Oppermann scribed: > "David G. Andersen" wrote: > > > > The last messages I saw in the archives about kern/73129 indicated > > that it was going to be fixed "shortly" > > > > (73129 is the "IPFW misbehavior in RELENG_5 thread" -- it's no longer > > possible to use ipfw fwd to perform policy routing). > > > > Sorry, it'll be fixed in 5.4-RELEASE. I have made up my mind how to > fix it the most correct way. Just a ping on this one - I've received several emails from people off the list asking if I'd found a fix for the problem. It seems like it would be grand if you could commit your fix to 5-STABLE instead of waiting for 5.4-RELEASE. -Dave -- Dave Andersen dga at cs dot cmu.edu Assistant Professor 412.268.3064 Carnegie Mellon University http://www.cs.cmu.edu/~dga