From: Mart Frauenlob <mart.frauenlob@chello.at>
To: netfilter@vger.kernel.org
Subject: Re: sync flood and resource utilization .
Date: Sun, 28 Feb 2010 10:19:03 +0100 [thread overview]
Message-ID: <4B8A3507.9020108@chello.at> (raw)
In-Reply-To: <cfeab66d1002262135x419e1009w8358c8c7f4def7cf@mail.gmail.com>
On 27.02.2010 06:36, netfilter-owner@vger.kernel.org wrote:
> iptables -A INPUT -j DROP .
> iptables -A OUTPUT -j ACCEPT
>
> When i syn flooded my desktop . I can see all pkts are getting
> rejected by the rule . But system becomes slow beacuse of this . Is
> there any way to make system fast ? will black listing will help ?
>
g00gle is your friend:
search: syn flood protection iptables
or:
syn flood protection iptables hashlimit recent blacklist
you can do some with a simple 'limit'.
or more complex with 'hashlimit' and 'recent'.
Best regards
Mart
next prev parent reply other threads:[~2010-02-28 9:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 5:35 sync flood and resource utilization ratheesh k
2010-02-27 7:09 ` lists
2010-02-27 12:10 ` ratheesh k
2010-02-28 9:19 ` Mart Frauenlob [this message]
2010-02-28 10:50 ` J. Bakshi
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=4B8A3507.9020108@chello.at \
--to=mart.frauenlob@chello.at \
--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