From owner-freebsd-net@FreeBSD.ORG Wed Feb 9 17:33:13 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 8EA6B16A4CE for ; Wed, 9 Feb 2005 17:33:13 +0000 (GMT) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4623943D2D for ; Wed, 9 Feb 2005 17:33:12 +0000 (GMT) (envelope-from oppermann@networx.ch) Received: (qmail 22758 invoked from network); 9 Feb 2005 17:11:42 -0000 Received: from unknown (HELO networx.ch) ([62.48.0.53]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 9 Feb 2005 17:11:42 -0000 Message-ID: <420A4957.15E0D656@networx.ch> Date: Wed, 09 Feb 2005 18:33:11 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: "David G. Andersen" References: <20050209170802.GA39472@lcs.mit.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org 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: Wed, 09 Feb 2005 17:33:13 -0000 "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). > > This bug is on my critical path for getting my network entirely swapped > over to 5.3 (b/c it breaks transparent proxying and other nifty games). > Could I beg Andre or someone to commit a fix that restores the old > behavior? > > (Barring that, has anyone patched it in their own system, and if so, > would you mind sending me the patch? I dislike running custom kernel > code on these machines, but I'm happy to do so to get things working. :) Sorry, it'll be fixed in 5.4-RELEASE. I have made up my mind how to fix it the most correct way. -- Andre