From: Florian Westphal <fw@strlen.de>
To: sontu mazumdar <sontu21@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Element-Level Logging Support in nftables Sets
Date: Sat, 28 Jun 2025 14:30:13 +0200 [thread overview]
Message-ID: <aF_gVaCX8789SYVl@strlen.de> (raw)
In-Reply-To: <CANgxkqwQpVQDM7AP20A0pCsGkPhte9tr-1gwdJJRVxqB9M2nng@mail.gmail.com>
sontu mazumdar <sontu21@gmail.com> wrote:
> I am exploring whether it's possible to add logging support at the
> element level within an nftables set. Specifically, I'm looking for
> functionality where an individual element in a set can trigger a log
> when it's matched—something like the following:
>
> table inet mytable {
> set s {
> typeof ip saddr
> counter
> elements = { 1.1.1.1 log prefix "element1" level info,
> 1.1.1.3 log prefix "element2" level info }
> }
> }
Could be done, however, typically "log" is combined with "limit" to
prevent log flooding.
> I understand that nftables sets currently do not support logging at
> the element level. Is there any plan to introduce this feature in
> future releases?
Not that I know of. Whats your use case?
prev parent reply other threads:[~2025-06-28 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 4:27 Element-Level Logging Support in nftables Sets sontu mazumdar
2025-06-28 12:30 ` Florian Westphal [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=aF_gVaCX8789SYVl@strlen.de \
--to=fw@strlen.de \
--cc=netfilter@vger.kernel.org \
--cc=sontu21@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).