From: Gianni Tedesco <gianni@ecsc.co.uk>
To: Patrick Michael Kane <modus-linux-kernel@pr.es.to>
Cc: linux-kernel@vger.kernel.org
Subject: Re: preventing route cache overflow
Date: 27 Feb 2003 13:21:14 +0000 [thread overview]
Message-ID: <1046352074.28559.20.camel@lemsip> (raw)
In-Reply-To: <20030227045017.A11619@pr.es.to>
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
On Thu, 2003-02-27 at 12:50, Patrick Michael Kane wrote:
> We recently had a server come under attack. Some script monkeys
> started generating a bunch of pings and SYNs from a huge variety of
> spoofed addresses (mostly in 43.0.0.0/8 and 44.0.0.0/8, for those that
> are interested).
>
> There were so many forged packets that the destination cache began to
> overflow hundreds or thousands of times per second ("kernel: dst cache
> overflow"). This had a huge negative impact on server performance.
Was this just syslog doing lots of write()+fsync() ? What kernel
version?
You should not get those messages that often in your logs, they should
be ratelimited:
linux-2.4.19/net/ipv4/route.c:598:
if (net_ratelimit())
printk(KERN_WARNING "dst cache overflow\n");
--
// Gianni Tedesco (gianni at scaramanga dot co dot uk)
lynx --source www.scaramanga.co.uk/gianni-at-ecsc.asc | gpg --import
8646BE7D: 6D9F 2287 870E A2C9 8F60 3A3C 91B5 7669 8646 BE7D
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-02-27 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 12:50 preventing route cache overflow Patrick Michael Kane
2003-02-27 13:21 ` Gianni Tedesco [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1046352074.28559.20.camel@lemsip \
--to=gianni@ecsc.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=modus-linux-kernel@pr.es.to \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.