From owner-cvs-all  Tue Aug 20 22:46:18 2002
Delivered-To: cvs-all@freebsd.org
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0237137B400; Tue, 20 Aug 2002 22:46:15 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id B786F43E65; Tue, 20 Aug 2002 22:46:14 -0700 (PDT)
	(envelope-from luigi@FreeBSD.org)
Received: from freefall.freebsd.org (luigi@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.4/8.12.4) with ESMTP id g7L5kEJU099199;
	Tue, 20 Aug 2002 22:46:14 -0700 (PDT)
	(envelope-from luigi@freefall.freebsd.org)
Received: (from luigi@localhost)
	by freefall.freebsd.org (8.12.4/8.12.4/Submit) id g7L5kEth099198;
	Tue, 20 Aug 2002 22:46:14 -0700 (PDT)
Message-Id: <200208210546.g7L5kEth099198@freefall.freebsd.org>
From: Luigi Rizzo <luigi@FreeBSD.org>
Date: Tue, 20 Aug 2002 22:46:14 -0700 (PDT)
To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: cvs commit: src/sbin/ipfw ipfw.8 ipfw2.c
X-FreeBSD-CVS-Branch: RELENG_4
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
List-ID: <cvs-all.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20cvs-all>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20cvs-all>
X-Loop: FreeBSD.ORG

luigi       2002/08/20 22:46:14 PDT

  Modified files:        (Branch: RELENG_4)
    sbin/ipfw            ipfw.8 ipfw2.c 
  Log:
  Sync ipfw2 with the version in -current:
  
  some changes in the syntax of ipfw2 extensions (ipfw1 syntax
  is not modified), add rule options to match IP addresses and
  ports, and MAC header fields.
  Make the parser more robust.
  
  Manpage updated and cleaned up to reflect the new syntax, and give
  examples.
  
  This commit closes all ipfw2 bug/feature reports I have received so far
  (hardly any of them were related to the kernel part, as you can tell
  from the commit logs), so i would seriously consider evaluating ipfw2
  for production use, especially if your firewall is running out of
  steam because you have complex rulesets handling sparse host sets.
  
  Have a look at the manpage, IPFW2 FEATURES and EXAMPLES Sections,
  to know about the new features.
  
  Revision   Changes    Path
  1.63.2.25  +159 -115  src/sbin/ipfw/ipfw.8
  1.4.2.5    +299 -136  src/sbin/ipfw/ipfw2.c

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message