Date: Wed, 17 Jul 2002 10:21:19 -0700 From: Luigi Rizzo <rizzo@icir.org> To: cjclark@alum.mit.edu Cc: ipfw@FreeBSD.ORG Subject: Re: Ouch! ipfw log and DoS Message-ID: <20020717102119.A12639@iguana.icir.org> In-Reply-To: <20020717165807.GA25404@blossom.cjclark.org>; from crist.clark@attbi.com on Wed, Jul 17, 2002 at 09:58:08AM -0700 References: <20020716124059.A2635@iguana.icir.org> <20020717064647.GC22967@blossom.cjclark.org> <20020717022619.A8351@iguana.icir.org> <20020717165807.GA25404@blossom.cjclark.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 17, 2002 at 09:58:08AM -0700, Crist J. Clark wrote: ... > I just really do not think that this is the right place for such a > limit. I don't like the idea that the firewall code just starts > dropping notifications without way to know about it. Think about what > happens for your example, a packet comes in that gets logged which > triggers a syslog cascade until we hit the limit. What we end up with > is only logging a small windows separated by at least a second, and > the logs are still almost entirely filled with the syslog feedback. the alternative being having your box hung until you hard-reset it, i know what i would choose :) cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ipfw" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020717102119.A12639>