From owner-freebsd-ipfw Tue Jul 9 2:32:10 2002 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 E798937B400; Tue, 9 Jul 2002 02:32:04 -0700 (PDT) Received: from iguana.icir.org (iguana.icir.org [192.150.187.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 372E143E31; Tue, 9 Jul 2002 02:32:04 -0700 (PDT) (envelope-from rizzo@iguana.icir.org) Received: (from rizzo@localhost) by iguana.icir.org (8.11.6/8.11.3) id g699W4R83312; Tue, 9 Jul 2002 02:32:04 -0700 (PDT) (envelope-from rizzo) Date: Tue, 9 Jul 2002 02:32:04 -0700 From: Luigi Rizzo To: ipfw@freebsd.org Subject: ipfw2 patches for -stable available Message-ID: <20020709023203.A83270@iguana.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-ipfw@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [Bcc to -stable as relevant there] As the subject says, the latest patches to run ipfw2 on -stable are at http://info.iet.unipi.it/~luigi/ipfw2.stable.020709.diffs They rely on the code that I have just committed to -stable. Once you have patched your source tree, you need to add options IPFW2 to your kernel config file to have the new functionality available, otherwise you will still use the old ipfw code. You also need to recompile /sbin/ipfw. Note that this patch *does not* handle libalias. (For the curious, ipfw2 is a nickname for the new firewall code which is in -current. It is much faster and more flexible than the old one, and implements the old ipfw syntax as a subset, so your existing configuration files should work unmodified -- and if they don't, please report the rule(s) where it chokes so i can fix that). cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ipfw" in the body of the message