From: "J. Bakshi" <joydeep@infoservices.in>
To: netfilter@vger.kernel.org
Subject: Re: limit module not working with drop policy
Date: Sun, 24 Jan 2010 20:53:16 +0530 [thread overview]
Message-ID: <20100124205316.098fbcbb@infoservices.in> (raw)
In-Reply-To: <4B5C208F.9090108@chello.at>
On Sun, 24 Jan 2010 11:27:27 +0100
Mart Frauenlob <mart.frauenlob@chello.at> wrote:
> > Thanks for your suggestion and hint. Now I have modified the rule
> > set as
> >
> > ` ` `
> > iptables -A INPUT -p icmp --icmp-type echo-request -m hashlimit \
> > --hashlimit 3/minute --hashlimit-name secureping -j ACCEPT
> > ` ` `
> >
> > but no luck yet :-( Is there anything wrong in my config ?
>
> What exactly are the error symptoms? What is not working?
> Please provide more information like kernel, iptables version.
> You could place LOG rules and/or TRACE rules to provide more
> information on what's going on.
>
The limit or hashlimit should protect my system by allowing only three ping request per minute ( as -m hashlimit --hashlimit 3/minute or same config by limit) . I saw it working before in debin lenny. I have upgrade my box into debian squeeze now and found the ping protection is not working at all. If I ping my box from outside; my box responds the ping per second !!!
So the ping protection is not working any more now :-( Just for reminder my firewall is default DROP and I have already posted iptables-save. Kindly ask me if you need any more information.
kernel version 2.6.31
iptables v1.4.6
next prev parent reply other threads:[~2010-01-24 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 3:24 limit module not working with drop policy J. Bakshi
2010-01-22 8:03 ` Remzi AKYÜZ
2010-01-23 9:45 ` Mart Frauenlob
2010-01-24 6:41 ` J. Bakshi
2010-01-24 10:27 ` Mart Frauenlob
2010-01-24 15:23 ` J. Bakshi [this message]
[not found] <4B595E9A.8090800@infoservices.in>
2010-01-23 7:02 ` 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=20100124205316.098fbcbb@infoservices.in \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox