From: Patrick McHardy <kaber@trash.net>
To: "Christoph A." <casmls@gmail.com>
Cc: Netfilter Developer Mailing List <netfilter-devel@vger.kernel.org>
Subject: Re: nftables: problem with sets (Object not found)
Date: Tue, 28 Jul 2009 14:23:22 +0200 [thread overview]
Message-ID: <4A6EEDBA.3010505@trash.net> (raw)
In-Reply-To: <4A69FCC3.1070404@gmail.com>
Christoph A. wrote:
> when trying to use sets ({ ..., ...}) I get the error "Object not found".
>
> This is my testscript:
> #! /usr/local/sbin/nft -f
>
>
> ...
> In file included from internal:0:0-0:
> ./set_problem:12:17-42: Error: Could not add rule: Object not found
> tcp dport { 22, 80} accept
> ^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Am I missing something in the kernel or do I have a syntax error in my
> rules?
> (kernel config attached)
I never pushed out the userspace changes for the new set API.
I just pushed out all the changes that should be needed, please
update your trees and try again.
next prev parent reply other threads:[~2009-07-28 12:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 18:26 nftables: problem with sets (Object not found) Christoph A.
2009-07-28 12:23 ` Patrick McHardy [this message]
2009-07-28 13:53 ` Patrick McHardy
2009-07-28 20:13 ` Christoph A.
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=4A6EEDBA.3010505@trash.net \
--to=kaber@trash.net \
--cc=casmls@gmail.com \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).