From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Binarus <lists@binarus.de>
Cc: netfilter@vger.kernel.org
Subject: Re: "nft list hooks" not working (empty output)
Date: Thu, 11 Jun 2026 01:15:15 +0200 [thread overview]
Message-ID: <ainwA_Lkyr85C6dB@chamomile> (raw)
In-Reply-To: <06c74ee3-64eb-47db-8575-bfe42eb47c4b@binarus.de>
On Thu, Jun 11, 2026 at 12:24:28AM +0200, Binarus wrote:
> Dear all,
>
> according to the man page for nft, "nft list hooks" should list all functions registered at each hook, along with their priorities, and including the internal nftables functions. I am understanding this in the sense that "nft list hooks" should output something at least when there actually is a ruleset.
>
> But on my test system, that output is always empty. Please consider the following excerpt from a terminal session:
>
> root@charon /etc/network # nft list ruleset
> table ip t_IP {
> chain input-filter {
> type filter hook input priority filter; policy accept;
> ip protocol icmp drop
> }
> }
> root@charon /etc/network # nft list hooks
> root@charon /etc/network #
>
> Of course, that ruleset does not make any sense, but it serves its purpose for testing. "nft list hooks" should output something in that situation, shouldn't it?
>
> This happens on Debian trixie, kernel 6.12.90, nftables 1.1.3.
>
> I also have tried "nft list hooks inet" with the same result.
>
> Furthermore, I have created another ruleset with an ingress filter and have tried "nft list hooks netdev", which also gave no output.
>
> Any advice or explanation? Where is my misunderstanding or mistake?
It seems debian kernels do not compile support for this command?
grep CONFIG_NETFILTER_NETLINK_HOOK /boot/config-6.12.74+deb13+1-amd64
# CONFIG_NETFILTER_NETLINK_HOOK is not set
next prev parent reply other threads:[~2026-06-10 23:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 22:24 "nft list hooks" not working (empty output) Binarus
2026-06-10 23:15 ` Pablo Neira Ayuso [this message]
2026-06-11 1:10 ` Kerin Millar
2026-06-11 5:32 ` Binarus
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=ainwA_Lkyr85C6dB@chamomile \
--to=pablo@netfilter.org \
--cc=lists@binarus.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