From: Florian Westphal <fw@strlen.de>
To: Frank Myhr <fmyhr@fhmtech.com>
Cc: Florian Westphal <fw@strlen.de>,
Frank Wunderlich <frank-w@public-files.de>,
netfilter@vger.kernel.org
Subject: Re: nft show counter
Date: Thu, 1 Apr 2021 20:21:04 +0200 [thread overview]
Message-ID: <20210401182104.GG13699@breakpoint.cc> (raw)
In-Reply-To: <d5770849-515b-5514-39ab-bb6907023ca2@fhmtech.com>
Frank Myhr <fmyhr@fhmtech.com> wrote:
> On 2021/03/31 17:40, Florian Westphal wrote:
> > You could use a named counter and then fetch it via 'nft list counter
> > inet tablenam countername'.
>
> This is the straightforward solution!
>
> Florian, is it correct that *all* counters are stateful objects, they're
> just anonymous stateful objects if used in a rule without first declaring
> them with a name? The wiki reads as if they're 2 separate things (I'm happy
> to fix but want to check with you first):
>
> https://wiki.nftables.org/wiki-nftables/index.php/Counters
The normal counters do not have a 'hidden' internal name.
Thats also the reason why simple counters do not show up in 'nft list counters',
they only exist in the context of the rule they are used in.
next prev parent reply other threads:[~2021-04-01 18:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 17:47 nft show counter Frank Wunderlich
2021-03-31 21:23 ` Frank Myhr
2021-03-31 21:40 ` Florian Westphal
2021-03-31 23:08 ` Frank Myhr
2021-04-01 8:08 ` Aw: " Frank Wunderlich
2021-04-01 16:42 ` Anton Rieger
2021-04-02 17:16 ` Frank Myhr
2021-04-02 17:42 ` Frank Wunderlich
2021-04-03 17:04 ` Frank Myhr
2021-04-02 22:22 ` Anton Rieger
2021-04-01 18:14 ` Florian Westphal
2021-04-01 18:31 ` Frank Wunderlich
2021-04-01 20:03 ` Florian Westphal
2021-04-02 11:58 ` Aw: " Frank Wunderlich
2021-04-02 17:10 ` Frank Myhr
2021-04-01 18:21 ` Florian Westphal [this message]
2021-07-22 19:57 ` manual : CONNTRACK EXPRESSIONS pauloric
2021-07-23 15:00 ` Pablo Neira Ayuso
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=20210401182104.GG13699@breakpoint.cc \
--to=fw@strlen.de \
--cc=fmyhr@fhmtech.com \
--cc=frank-w@public-files.de \
--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