Date: Mon, 19 Jun 2000 10:59:45 +0200 From: Marc Silver <marcs@draenor.org> To: Giorgos Keramidas <keramida@ceid.upatras.gr> Cc: The Clark Family <res03db2@gte.net>, freebsd-questions@FreeBSD.ORG Subject: Re: Updating ipfw at dhcp induced ip address change. Message-ID: <20000619105945.F26533@draenor.org> In-Reply-To: <20000619125418.A2251@hades.hell.gr>; from keramida@ceid.upatras.gr on Mon, Jun 19, 2000 at 12:54:18PM %2B0300 References: <20000619003156.A642@hades.hell.gr> <Pine.BSF.4.21.0006171503010.38057-100000@orthanc.dsl.gtei.net> <20000619125418.A2251@hades.hell.gr>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000619105945.F26533>