From: Patrick McHardy <kaber@trash.net>
To: netfilter@vger.kernel.org
Subject: Re: conntrack is bad during DDoS?
Date: Mon, 08 Oct 2007 10:46:48 +0200 [thread overview]
Message-ID: <4709EE78.4010005@trash.net> (raw)
In-Reply-To: <47056569.3020704@andrei.myip.org>
Florin Andrei wrote:
> Florin Andrei wrote:
>
>> I understand the thing about stateless NAT and 2.6.24 - that's very
>> good news, too bad it's not in older versions. :-)
>
>
> Come to think of it, I need explanations for this one too. :-)
> Is that true only for 1:1 NAT, or NAT in general? If the former, is that
> a special new case, requiring different iptables rules, or something else?
Its implemented as TC action, so its independant of iptables. It only
supports 1:1 NAT, everything else needs to be stateful to avoid clashes.
> I assume these are recent changes to netfilter - is there a place where
> I can find these specific changes documented or discussed?
Check the netdev archives of the past two or three weeks.
next prev parent reply other threads:[~2007-10-08 8:46 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 [this message]
2007-10-08 8:45 ` Patrick McHardy
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=4709EE78.4010005@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