From: Andre Uratsuka Manoel <andreum@gmail.com>
To: netdev@oss.sgi.com
Subject: route cache overflow
Date: Tue, 6 Jul 2004 00:33:15 -0300 [thread overview]
Message-ID: <e7fcadd304070520335b493747@mail.gmail.com> (raw)
Hello,
It seems that no resolution was found for the route cache DoS issue
(am I wrong here?).
I was wondering, and I'd like to persue this line of thought if you
don't consider this stupid: wouldn't it be better, when we find that
the machine is under DoS to avoid creating route cache entries instead
of simply trying to drop entries that exist?
Couldn't we create entries only once for every 1<<n packets on
ip_route_input_slow so that flows with many packets will have route
cache entries created with higher probability than flows with very
little connections. The n variable could be adjusted according to
perceived DoS-ness.
Is this stupid?
Andre
next reply other threads:[~2004-07-06 3:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-06 3:33 Andre Uratsuka Manoel [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-17 11:26 route cache overflow Robert Olsson
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=e7fcadd304070520335b493747@mail.gmail.com \
--to=andreum@gmail.com \
--cc=andre@insite.com.br \
--cc=netdev@oss.sgi.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).