On Wed, Dec 13, 2000 at 02:42:53PM -0500, Richard A. Steenbergen wrote:
> It could just as easily be a SYN flood against a single port... or a large
> number of clients trying to connected to your crashed web server... :P Or
> it could just as easily be an ack flood against a port without a listener
> and be showing up in the "not the ack flood" counter.
Exactly. Bikeshedding the millions of possible reasons the queue/ratelimit
was triggered is silly.
Bosko, please change the descriptions to something very generic before
committing them ("ratelimiting TCP RST packets: x/y pps" or something)
--
Bill Fumerola - security yahoo / Yahoo! inc.
- [EMAIL PROTECTED] / [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
- Ratelimint Enhancement patch (Please Review One Las... Bosko Milekic
- Re: Ratelimint Enhancement patch (Please Revie... Richard A. Steenbergen
- Re: Ratelimint Enhancement patch (Please R... Alfred Perlstein
- Re: Ratelimint Enhancement patch (Plea... Richard A. Steenbergen
- Re: Ratelimint Enhancement patch (... Bill Fumerola
- Re: Ratelimint Enhancement pa... Bosko Milekic
- Re: Ratelimint Enhancemen... Bill Fumerola
- Re: Ratelimint Enhancement patch (... Don Lewis
- Re: Ratelimint Enhancement patch (Please R... Mike Silbersack
- Re: Ratelimint Enhancement patch (Plea... Richard A. Steenbergen
- Re: Ratelimint Enhancement patch (... Mike Silbersack
- Re: Ratelimint Enhancement pa... Richard A. Steenbergen
- Re: Ratelimint Enhancemen... Mike Silbersack
- Re: Ratelimint Enhanc... Richard A. Steenbergen
