From: "Serguei Bezverkhi (sbezverk)" <sbezverk@cisco.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>,
"netfilter-devel@vger.kernel.org"
<netfilter-devel@vger.kernel.org>
Subject: Missing SetID
Date: Mon, 12 Aug 2019 18:14:41 +0000 [thread overview]
Message-ID: <60AFF2FD-1567-4D49-B870-580520BEF17A@cisco.com> (raw)
In-Reply-To: <372F88D9-353F-428C-9B59-A8D4D7BF5438@cisco.com>
Hello,
I am observing a strange condition at least imho, when a set gets programmed or lookup expression with setid is programmed, when I do GETSETS or GETRULES, the set ID is always 0, but Set name is correctly preserved. If SetID is not preserved then how would be possible to differentiate between multiple anonymous sets defined for the same table?
I would appreciate some clarification. I am positive that ID gets sent to kernel in both cases, but return messages is missing SET_ID attribute.
Thank you
Serguei
parent reply other threads:[~2019-08-12 18:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <372F88D9-353F-428C-9B59-A8D4D7BF5438@cisco.com>]
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=60AFF2FD-1567-4D49-B870-580520BEF17A@cisco.com \
--to=sbezverk@cisco.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).