From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Robert Sander <r.sander@heinlein-support.de>
Cc: netfilter <netfilter@vger.kernel.org>,
Shivani Bhardwaj <shivanib134@gmail.com>
Subject: Re: nftables rate limit logging and then drop
Date: Wed, 9 Dec 2015 22:44:13 +0100 [thread overview]
Message-ID: <20151209214413.GA20365@salvia> (raw)
In-Reply-To: <565F73F5.3090004@heinlein-support.de>
On Wed, Dec 02, 2015 at 11:43:01PM +0100, Robert Sander wrote:
> Hi,
>
> How do I implement something like this in nftables:
>
> iptables -A INPUT -m conntrack --ctstate INVALID -m limit --limit 3/m --limit-burst 5 -j LOG --log-level debug --log-prefix "INVALID DROP: "
> iptables -A INPUT -m conntrack --ctstate INVALID -j DROP
The translation is:
nft add rule filter input ct state invalid \
limit rate 3/minute burst 5 packets \
log level debug prefix \"INVALID DROP: \" counter
nft add rule filter input ct state invalid counter drop
Note that rule counters are optional in nftables, unlikely iptables
where we always have them on.
prev parent reply other threads:[~2015-12-09 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 22:43 nftables rate limit logging and then drop Robert Sander
2015-12-09 21:44 ` Pablo Neira Ayuso [this message]
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=20151209214413.GA20365@salvia \
--to=pablo@netfilter.org \
--cc=netfilter@vger.kernel.org \
--cc=r.sander@heinlein-support.de \
--cc=shivanib134@gmail.com \
/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.