From owner-freebsd-stable@FreeBSD.ORG Sun Jul 4 12:35:35 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 893F816A4CE; Sun, 4 Jul 2004 12:35:35 +0000 (GMT) Received: from mta11.adelphia.net (mta11.adelphia.net [68.168.78.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DE9643D1D; Sun, 4 Jul 2004 12:35:35 +0000 (GMT) (envelope-from Barbish3@adelphia.net) Received: from barbish ([67.20.101.71]) by mta11.adelphia.net (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with SMTP id <20040704123534.OIUF13168.mta11.adelphia.net@barbish>; Sun, 4 Jul 2004 08:35:34 -0400 From: "JJB" To: "Rob" , , , Date: Sun, 4 Jul 2004 08:35:33 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <40E7F4D7.5040904@users.sourceforge.net> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Importance: Normal Subject: RE: IPFIREWALL_VERBOSE_LIMIT ignored by recent kernel/world? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Barbish3@adelphia.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jul 2004 12:35:35 -0000 Adding an "logamount" option to each logging rules would be to "long way work around". Adding net.inet.ip.fw.verbose_limit=100 to /etc/sysctl.conf would be the short way. -----Original Message----- From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Rob Sent: Sunday, July 04, 2004 8:15 AM To: freebsd-stable@freebsd.org; freebsd-questions@freebsd.org; freebsd-current@freebsd.org Subject: Re: IPFIREWALL_VERBOSE_LIMIT ignored by recent kernel/world? Dan Pelleg wrote: > I have a patch for that in kern/46080. Note I haven't tested it in a while > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/46080 > So what I observed (security logfile get floaded with ipfw2 logs) is actually a kind of bug. If so, I'd rather wait till the fix makes it into the official sources. If not, then I won't change my own sources. Work around for now could be to add a "logamount" statement to each of the logging rules of ipfw2. Right? Thanks! Regards, Rob. PS: does this problem also occur in CURRENT, which uses by default IPFW2 ? _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"