From owner-freebsd-ipfw@FreeBSD.ORG Thu Jun 24 07:40:45 2004 Return-Path: Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98B1116A4CE; Thu, 24 Jun 2004 07:40:45 +0000 (GMT) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 782BC43D49; Thu, 24 Jun 2004 07:40:45 +0000 (GMT) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.9p1/8.12.8) with ESMTP id i5O7eggd062938; Thu, 24 Jun 2004 00:40:42 -0700 (PDT) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.9p1/8.12.3/Submit) id i5O7eeH0062937; Thu, 24 Jun 2004 00:40:40 -0700 (PDT) (envelope-from rizzo) Date: Thu, 24 Jun 2004 00:40:39 -0700 From: Luigi Rizzo To: Nick Rogness Message-ID: <20040624004039.A62893@xorpc.icir.org> References: <200406240636.i5O6adNV000825@ns.networkersbg.com> <20040624064350.GA62743@ip.net.ua> <20040624010726.H5174@skywalker.rogness.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20040624010726.H5174@skywalker.rogness.net>; from nick@rogness.net on Thu, Jun 24, 2004 at 01:09:14AM -0600 cc: freebsd-ipfw@freebsd.org cc: Evgeny Ivanov Subject: Re: tables in ipfw2 X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jun 2004 07:40:45 -0000 On Thu, Jun 24, 2004 at 01:09:14AM -0600, Nick Rogness wrote: ... > Is there any reason why IPFW2 has not become the standard > IPFW...still not stable enough or ??? IPFW2 is backwards > compatible with IPFW is it not? at the time people wanted to check it for a while to make sure there weren't issues. I guess that given the option, this satisfied both worlds, so nobody cared to change the standard (the only reason for doing that would be remove ipfw1 at the next time there is a system change that would require an ipfw1 patch). cheers luigi