From owner-freebsd-current@FreeBSD.ORG Sun Jul 4 12:15:23 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB55C16A4CE; Sun, 4 Jul 2004 12:15:23 +0000 (GMT) Received: from auk1.snu.ac.kr (auk1.snu.ac.kr [147.46.100.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D39F43D5E; Sun, 4 Jul 2004 12:15:23 +0000 (GMT) (envelope-from stopspam@users.sourceforge.net) Received: from [147.46.44.181] (stopspam@users.sourceforge.net) by auk1.snu.ac.kr (Terrace Internet Messaging Server) with ESMTP id 2004070421:15:04:836315.24099.2577918896 for ; Sun, 04 Jul 2004 21:15:04 +0900 (KST) Message-ID: <40E7F4D7.5040904@users.sourceforge.net> Date: Sun, 04 Jul 2004 21:15:19 +0900 From: Rob User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040703 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org, freebsd-current@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-TERRACE-SPAMMARK: NO (SR:5.30) (by Terrace) X-Mailman-Approved-At: Sun, 04 Jul 2004 12:45:18 +0000 Subject: Re: IPFIREWALL_VERBOSE_LIMIT ignored by recent kernel/world? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jul 2004 12:15:24 -0000 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 ?