From: Florian Westphal <fw@strlen.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Florian Westphal <fw@strlen.de>,
netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Re: nftables: syntax ambiguity with objref map and ct helper objects
Date: Mon, 31 Jul 2023 14:46:37 +0200 [thread overview]
Message-ID: <20230731124637.GA7056@breakpoint.cc> (raw)
In-Reply-To: <ZMenriLfu+luvh9i@calendula>
Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> Hi Florian,
>
> On Fri, Jul 28, 2023 at 09:56:14PM +0200, Florian Westphal wrote:
> > Hi,
> >
> > I wanted to allow creating objref maps that
> > return "ct timeout" or "ct helper" templates.
> >
> > However:
> > map .. {
> > type ipv4_addr : ct timeout
> >
> > The above is fine, but this is not:
> >
> > map .. {
> > type ipv4_addr : ct helper
>
> This is type, not typeof, is it intentional?
Yes, but doesn't matter for this problem.
Same ambiguity with
typeof ip saddr : ct helper
> This works fine with typeof:
>
> table ip x {
> map x {
> typeof ip saddr : ct helper
> }
> }
My point is how nft should differentiate between
ct helper "bla" {
rule add ct helper "foo"
In above map declaration. What does
"typeof ip saddr : ct helper" declare?
As far as I can see its arbitrary 16-byte strings, so the
above doesn't delcare an objref map that maps ip addresses
to conntrack helper templates.
next prev parent reply other threads:[~2023-07-31 12:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 19:56 nftables: syntax ambiguity with objref map and ct helper objects Florian Westphal
2023-07-31 12:23 ` Pablo Neira Ayuso
2023-07-31 12:46 ` Florian Westphal [this message]
2023-07-31 15:32 ` Pablo Neira Ayuso
2023-08-04 9:12 ` Florian Westphal
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=20230731124637.GA7056@breakpoint.cc \
--to=fw@strlen.de \
--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 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.