From: Patrick McHardy <kaber@trash.net>
To: netfilter@vger.kernel.org
Subject: Re: conntrack is bad during DDoS?
Date: Mon, 08 Oct 2007 10:45:18 +0200 [thread overview]
Message-ID: <4709EE1E.2060206@trash.net> (raw)
In-Reply-To: <470562BF.3090504@andrei.myip.org>
[Please keep me CCed]
Florin Andrei wrote:
> Patrick McHardy wrote:
>
>>
>> Please try 2.6.23 once its out (or the current -rc), it should behave
>> better.
>>
>> 2.6.24 will include stateless NAT again for 1:1 mappings.
>
>
> So, can you elaborate a little bit?
> I understand the thing about stateless NAT and 2.6.24 - that's very good
> news, too bad it's not in older versions. :-)
>
> But what's different in 2.6.23-rc that will make it better in my situation?
The eviction algorithms scans up to a maximum of 8 entries before
giving up instead of stopping at the end of the hash chain (which
is a single entry with a properly sized hash). So the chances
of finding an unconfirmed entry to evict are better.
prev parent reply other threads:[~2007-10-08 8:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 21:53 conntrack is bad during DDoS? Florin Andrei
2007-10-04 9:22 ` Patrick McHardy
2007-10-04 22:01 ` Florin Andrei
2007-10-04 22:12 ` Florin Andrei
2007-10-08 8:46 ` Patrick McHardy
2007-10-08 8:45 ` Patrick McHardy [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=4709EE1E.2060206@trash.net \
--to=kaber@trash.net \
--cc=netfilter@vger.kernel.org \
/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