From owner-cvs-all  Sun Aug  1  9:57:37 1999
Delivered-To: cvs-all@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 2C74314C81; Sun,  1 Aug 1999 09:57:31 -0700 (PDT)
	(envelope-from green@FreeBSD.org)
Received: (from green@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id JAA44866;
	Sun, 1 Aug 1999 09:57:25 -0700 (PDT)
	(envelope-from green@FreeBSD.org)
Message-Id: <199908011657.JAA44866@freefall.freebsd.org>
From: Brian Feldman <green@FreeBSD.org>
Date: Sun, 1 Aug 1999 09:57:25 -0700 (PDT)
To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: cvs commit: src/sys/netinet in.h ip_fw.c ip_fw.h raw_ip.c
         src/sbin/ipfw ipfw.8 ipfw.c
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk

green       1999/08/01 09:57:25 PDT

  Modified files:
    sys/netinet          in.h ip_fw.c ip_fw.h raw_ip.c 
    sbin/ipfw            ipfw.8 ipfw.c 
  Log:
    Make ipfw's logging more dynamic. Now, log will use the default limit
  _or_ you may specify "log logamount number" to set logging specifically
  the rule.
     In addition, "ipfw resetlog" has been added, which will reset the
  logging counters on any/all rule(s). ipfw resetlog does not affect
  the packet/byte counters (as ipfw reset does), and is the only "set"
  command that can be run at securelevel >= 3.
     This should address complaints about not being able to set logging
  amounts, not being able to restart logging at a high securelevel,
  and not being able to just reset logging without resetting all of the
  counters in a rule.
  
  Revision  Changes    Path
  1.43      +2 -1      src/sys/netinet/in.h
  1.116     +80 -9     src/sys/netinet/ip_fw.c
  1.40      +3 -1      src/sys/netinet/ip_fw.h
  1.60      +2 -1      src/sys/netinet/raw_ip.c
  1.55      +25 -8     src/sbin/ipfw/ipfw.8
  1.72      +72 -3     src/sbin/ipfw/ipfw.c



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