From owner-freebsd-questions Mon Jun 19 2: 1:59 2000 Delivered-To: freebsd-questions@freebsd.org Received: from draenor.org (draenor.org [196.36.119.129]) by hub.freebsd.org (Postfix) with ESMTP id 8750337BC3E for ; Mon, 19 Jun 2000 02:01:53 -0700 (PDT) (envelope-from marcs@draenor.org) Received: from marcs by draenor.org with local (Exim 3.14 #1) id 133xPF-0007O2-00; Mon, 19 Jun 2000 10:59:45 +0200 Date: Mon, 19 Jun 2000 10:59:45 +0200 From: Marc Silver To: Giorgos Keramidas Cc: The Clark Family , freebsd-questions@FreeBSD.ORG Subject: Re: Updating ipfw at dhcp induced ip address change. Message-ID: <20000619105945.F26533@draenor.org> References: <20000619003156.A642@hades.hell.gr> <20000619125418.A2251@hades.hell.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000619125418.A2251@hades.hell.gr>; from keramida@ceid.upatras.gr on Mon, Jun 19, 2000 at 12:54:18PM +0300 X-Operating-System: FreeBSD 4.0-STABLE Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jun 19, 2000 at 12:54:18PM +0300, Giorgos Keramidas wrote: > The only case where I can think of manual intervention as being > necessary with a finished ipfw setup is when you have rules that log > packets, and a logamount that limits how many times this rule will be > logged. In such a case, after a while, you might have to run > > # ipfw zero > > only to make sure that the hit count of every rule is zeroed again. > This does not mean that without "ipfw zero" the rule does not work, > though. It does work, as long as it's there. It simply does not log > rule hits any more to syslogd. Yes, this is something that confused me in the beginning as well. You can also use "ipfw resetlog" to do this. :) I just run it from cron every day. :) Cheers, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message