From owner-freebsd-current@FreeBSD.ORG Fri Aug 4 10:12:04 2006 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1684116A4DA for ; Fri, 4 Aug 2006 10:12:04 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B17143D45 for ; Fri, 4 Aug 2006 10:12:03 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.4/8.13.3) with ESMTP id k74AAsOk035086 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Aug 2006 14:10:54 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.4/8.13.1/Submit) id k74AAr8W035085; Fri, 4 Aug 2006 14:10:53 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Fri, 4 Aug 2006 14:10:52 +0400 From: Gleb Smirnoff To: Julian Elischer Message-ID: <20060804101052.GW96644@FreeBSD.org> References: <44D1473F.1000204@elischer.org> <44D150D6.6010101@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <44D150D6.6010101@elischer.org> User-Agent: Mutt/1.5.6i Cc: current@FreeBSD.org Subject: Re: Ignore: Re: ipfw output FWD broken on 6.1 and newer? 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: Fri, 04 Aug 2006 10:12:04 -0000 On Wed, Aug 02, 2006 at 06:26:46PM -0700, Julian Elischer wrote: J> >I haven't tried 7.x yet but has anyone seen J> >the FWD command of ipfw running on 6.1? J> > J> >or anyone know of problems with it that may have been fixed on -current? J> J> Just found the "EXTENDED" option for ipfw fwd. J> J> Why we need that is wierd since it just allows it to act as it always J> used to and it never J> aused any massive problems that I know of (I committed it originally). J> personally I consider removing the option and making it default or J> reversing it and J> calling it J> J> IPFIREWALL_FORWARD_CRIPPLED I'm suprised that you have noticed it only now. When Andre has introduced this option that turns on a functionality that was present always before, I was quite angry but everyone ignored me. This even went to release notes as "new feature". -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE