From: Marek Kierdelewicz <marek@piasta.pl>
To: "J. Bakshi" <joydeep@infoservices.in>
Cc: netfilter@vger.kernel.org
Subject: Re: Hot to design syn-flood protection based on ip ?
Date: Tue, 1 Sep 2009 10:12:16 +0200 [thread overview]
Message-ID: <20090901101216.06ced847@catlap> (raw)
In-Reply-To: <4A9CCF5C.8050100@infoservices.in>
Hello,
>Thanks a lot, what about this ruleset ?
>iptables -A INPUT -p tcp --syn -m hashlimit \
> --hashlimit 1/sec --hashlimit-burst 4 --hashlimit-htable-expire 300000
>\ --hashlimit-mode srcip --hashlimit-name testlimit -j ACCEPT
>iptables -A INPUT -j DROP
>The concept here the blocked ip doing the syn-flood will be blacklisted
>for 5 min and will be checked again after that interval.
I think it won't work as a blacklist just drop syns that are above
1/sec. Option htable-expire is not for blacklisting but for setting
timeframe in which hashlimit is operating (eg. it won't work well if you
set htable-expire to 300s and have hashlimit set to 20/hour). To obtain
desired effect you can use recent module (great work by Stephen Frost
by the way):
iptables -A INPUT -m recent --name blacklist --rcheck --seconds 300 \
-j DROP
iptables -A INPUT -p tcp --syn -m hashlimit \
--hashlimit 1/sec --hashlimit-burst 4 --hashlimit-htable-expire 300000\
--hashlimit-mode srcip --hashlimit-name testlimit -j ACCEPT
iptables -A INPUT -m recent --name blacklist --set -j DROP
You can find more information about recent here:
- http://snowman.net/projects/ipt_recent/
- and in manpage;
Best regards,
Marek
next prev parent reply other threads:[~2009-09-01 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 12:36 Hot to design syn-flood protection based on ip ? J. Bakshi
2009-09-01 6:28 ` J. Bakshi
2009-09-01 6:58 ` Marek Kierdelewicz
2009-09-01 7:38 ` J. Bakshi
2009-09-01 8:12 ` Marek Kierdelewicz [this message]
2009-09-01 8: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=20090901101216.06ced847@catlap \
--to=marek@piasta.pl \
--cc=joydeep@infoservices.in \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.