From: trentbuck@gmail.com (Trent W. Buck)
To: netfilter@vger.kernel.org
Subject: Re: nftables v0.9.0 netlink: Error: set is not a map
Date: Tue, 22 Oct 2019 11:30:26 +1100 [thread overview]
Message-ID: <87sgnld3kt.fsf@goll.lan> (raw)
In-Reply-To: 37d8e802-87c2-4ef6-d0da-173bbd2ded60@tootai.net
Daniel Huhardeaux <tech@tootai.net> writes:
> I created a bash script under Debian/Buster to create nft rules: it
> works perfectly.
>
> Now I copy this script to a Debian/Stretch machine (nftables v0.7.0)
> and get in troubles to make it work: at some point I receive the
> subject error.
>
> OK, I think it's a version problem: I installed nftables from Stretch
> backports which is the same version as the Buster one, v0.9.0 But
> bang, error is still here :(
>
> What can be the cause of this error? Yes, I use sets, and no, they are
> no maps defined.
Can you show us your actual ruleset.nft?
Or (better yet) distill it down to a minimal test ruleset.nft that
generates the problem, and show us that.
I don't recognize the specific error.
I have seen similar errors before due to brainos in my ruleset.
I agree it doesn't make sense that the same version (nftables=0.9.0 on
Debian 9 and Debian 10) should parse the same way - so maybe it's a
difference on the kernel side?
Are you running
4.19.67-2+deb10u1~bpo9+1 on Debian 9, and
4.19.67-2 on Debian 10?
next prev parent reply other threads:[~2019-10-22 0:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 20:08 nftables v0.9.0 netlink: Error: set is not a map Daniel Huhardeaux
2019-10-22 0:30 ` Trent W. Buck [this message]
2019-10-22 8:31 ` Daniel Huhardeaux
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=87sgnld3kt.fsf@goll.lan \
--to=trentbuck@gmail.com \
--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.