From: "J. Bakshi" <joydeep@infoservices.in>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Richard Horton <arimus.uk@googlemail.com>, netfilter@vger.kernel.org
Subject: Re: ssh overflow blacklisting not working properly
Date: Mon, 29 Mar 2010 16:52:21 +0530 [thread overview]
Message-ID: <4BB08D6D.4050700@infoservices.in> (raw)
In-Reply-To: <alpine.LSU.2.01.1003291303410.16683@obet.zrqbmnf.qr>
On 03/29/2010 04:35 PM, Jan Engelhardt wrote:
> On Monday 2010-03-29 12:51, J. Bakshi wrote:
>
>> On 03/29/2010 01:48 PM, Richard Horton wrote:
>>
>>> On 29 March 2010 08:31, J. Bakshi <joydeep@infoservices.in> wrote:
>>>
>>>
>>>> iptables -A INPUT -p tcp -m state --state NEW --dport $SSH_PORT -m
>>>> hashlimit \
>>>> --hashlimit 3/min --hashlimit-burst 1 --hashlimit-htable-expire 180000 \
>>>> --hashlimit-mode srcip --hashlimit-name sshlimit -j ACCEPT
>>>>
>>>> #----------------------------------------#
>>>>
>>>> As expected connection attempt more than 3 in a min is dropped and
>>>> ensure only 3 connection per minute. But It should also block the source
>>>> IP for 3 min and this part is not working here.
>>>>
> It should not block it, it's not part of the definition of the
> S-TBF (or any other) limiter. You have to use -m recent as a list
> to store entries once they have gone over their limit.
>
>
Could you kindly enlighten me in that direcxtion with possibly little
examples.
thanks
--
জয়দীপ বক্সী
next prev parent reply other threads:[~2010-03-29 11:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 7:31 ssh overflow blacklisting not working properly J. Bakshi
2010-03-29 8:18 ` Richard Horton
2010-03-29 10:51 ` J. Bakshi
2010-03-29 11:05 ` Jan Engelhardt
2010-03-29 11:22 ` J. Bakshi [this message]
2010-03-29 11:22 ` J. Bakshi
2010-03-29 11:54 ` Richard Horton
2010-03-29 15:10 ` J. Bakshi
2010-03-30 7:42 ` J. Bakshi
2010-03-30 8:23 ` Richard Horton
2010-03-30 8:52 ` 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=4BB08D6D.4050700@infoservices.in \
--to=joydeep@infoservices.in \
--cc=arimus.uk@googlemail.com \
--cc=jengelh@medozas.de \
--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