From: "Remzi AKYÜZ" <linuxliste@gmail.com>
To: "J. Bakshi" <joydeep@infoservices.in>
Cc: netfilter@vger.kernel.org
Subject: Re: limit module not working with drop policy
Date: Fri, 22 Jan 2010 10:03:36 +0200 [thread overview]
Message-ID: <4B595BD8.4090009@gmail.com> (raw)
In-Reply-To: <4B591A79.2030600@infoservices.in>
Hello,
can you send
output of the iptables-save?
J. Bakshi wrote:
> Dear list,
>
> My firewall policy is default drop. But the limit module is not working
> here. I have the following rules to defeat ping flood
>
> ``````````
> iptables -A INPUT -p icmp -m limit --limit 3/minute -j ACCEPT
> iptables -A INPUT -p icmp -j DROP
> ``````````````````
> and it is not working. The same rule set is working with default accept
> policy. What modification should I need to make it working with drop
> policy firewall ?
>
> Thanks
>
>
>
>
next prev parent reply other threads:[~2010-01-22 8:03 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 [this message]
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
[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=4B595BD8.4090009@gmail.com \
--to=linuxliste@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox