From: Florian Westphal <fw@strlen.de>
To: ѽ҉ᶬḳ℠ <vtol@gmx.net>
Cc: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: [nftables] log flood protection?
Date: Fri, 25 Sep 2020 11:31:19 +0200 [thread overview]
Message-ID: <20200925093119.GB31471@breakpoint.cc> (raw)
In-Reply-To: <a3a88c99-9164-f56a-6368-d59230c647e6@gmx.net>
ѽ҉ᶬḳ℠ <vtol@gmx.net> wrote:
> Trying to limit log entries as a preventive measure for log flooding with
>
> log flags all prefix "foo DROP: " limit rate 1/second
This applies the limit after the log has taken place.
limit rate 1/second log flags ...
next prev parent reply other threads:[~2020-09-25 9:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 8:31 [nftables] log flood protection? ѽ҉ᶬḳ℠
2020-09-25 9:31 ` Florian Westphal [this message]
2020-09-25 9:41 ` ѽ҉ᶬḳ℠
-- strict thread matches above, loose matches on Subject: below --
2020-09-25 9:03 ѽ҉ᶬḳ℠
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=20200925093119.GB31471@breakpoint.cc \
--to=fw@strlen.de \
--cc=netfilter@vger.kernel.org \
--cc=vtol@gmx.net \
/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