Date: Sun, 4 Jul 2004 08:35:33 -0400 From: "JJB" <Barbish3@adelphia.net> To: "Rob" <stopspam@users.sourceforge.net>, <freebsd-stable@freebsd.org>, <freebsd-questions@freebsd.org>, <freebsd-current@freebsd.org> Subject: RE: IPFIREWALL_VERBOSE_LIMIT ignored by recent kernel/world? Message-ID: <MIEPLLIBMLEEABPDBIEGMECIGFAA.Barbish3@adelphia.net> In-Reply-To: <40E7F4D7.5040904@users.sourceforge.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?MIEPLLIBMLEEABPDBIEGMECIGFAA.Barbish3>