From: Nathan Wagner <nw@hydaspes.if.org>
To: netfilter@vger.kernel.org
Subject: Re: nft list empty
Date: Tue, 26 Oct 2021 20:58:54 +0000 [thread overview]
Message-ID: <YXhsDm0P7BOS3l98@granicus.if.org> (raw)
In-Reply-To: <bb50c53c-f365-92b9-87c5-193a77ca3ace@freenet.de>
On Tue, Oct 26, 2021 at 10:32:15PM +0200, Benno wrote:
> Am 26.10.21 um 21:28 schrieb Nathan Wagner:
> > For some reason, 'nft list ...' doesn't seem to print anything out.
> > A nft create table seems to create the table, but other than an
> > error if I try to create it again, I don't have any way to tell.
> >
>
> Which version of nftables are you using?
1.0.0
> Does nft list tables or nft list chains output your rules?
No, I added a '/usr/sbin/nft list tables' and '/usr/sbin/nft list
chains' to the appropriate places in my repro script, and they don't
produce any output.
> (Kernel 4.15 is from 2018, most major distributions moved to at least
> 4.19.
I think 4.15 should still support nftables. I've got a more recent
kernel compiled and packaged, but my uptime is 848 days...
> Currently nftables 1.0.0 is stable but not yet available in all
> distributions.)
>
> Is nft really the binary from the nftables package
Yes, which I can guarantee, since I compiled it myself.
> or something wrapped/enhanced by a distribution?
No, that's not it. I packaged it myself. I also tried running the
binary straight from the compilation directory.
> Is there an alias in your shell? (In Bash this can be avoided by using
> 'nft' ??? single quotes.)
No alias. I changed my repro script to call /usr/sbin/nft rather than
just 'nft', same result.
--
nw
next prev parent reply other threads:[~2021-10-26 20:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 19:28 nft list empty Nathan Wagner
2021-10-26 20:32 ` Benno
2021-10-26 20:58 ` Nathan Wagner [this message]
2021-10-26 22:40 ` Pablo Neira Ayuso
2021-10-27 5:49 ` Nathan Wagner
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=YXhsDm0P7BOS3l98@granicus.if.org \
--to=nw@hydaspes.if.org \
--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 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.