From: "SB CH" <chulmin2@hotmail.com>
To: netfilter@lists.netfilter.org
Subject: iptables can protect syn-flooding?
Date: Wed, 06 Nov 2002 05:01:33 +0000 [thread overview]
Message-ID: <F124l1k7ZDGRLvoD6ax0001857d@hotmail.com> (raw)
Hello all.
I saw that we can protect syn-flooding using iptables like this.
$IPTABLES -N syn-flood
$IPTABLES -A INPUT -p tcp --syn -j syn-flood
$IPTABLES -A syn-flood -m limit --limit 1/s --limit-burst 4 -j RETURN
$IPTABLES -A syn-flood -j DROP
But I think that anyone can't protect syn-flooding attack completely using
this rule, just some legal client can't connect the server because the rate
limit rule in busy system.
I guess that any firewall can't protect syn-flooding except tcp intercept
method.right?
(but tcp intercept requires so much memory)
any idea?
Thanks in advance.
_________________________________________________________________
증권 정보 가장 빠르고 편하게 보실 수 있습니다. MSN 증권/투자
http://www.msn.co.kr/stock/
next reply other threads:[~2002-11-06 5:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 5:01 SB CH [this message]
2002-11-06 15:06 ` iptables can protect syn-flooding? Jon Anderson
2002-11-06 17:17 ` Antony Stone
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=F124l1k7ZDGRLvoD6ax0001857d@hotmail.com \
--to=chulmin2@hotmail.com \
--cc=netfilter@lists.netfilter.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