From: "Kerin Millar" <kfm@plushkava.net>
To: netfilter@vger.kernel.org
Subject: Re: Sets nesting/reference? Complex concatenations in vmaps?
Date: Thu, 09 May 2024 13:54:47 +0100 [thread overview]
Message-ID: <dd5723aa-6516-4cfc-9a24-bc3e599dda54@app.fastmail.com> (raw)
In-Reply-To: <20240509124230.6e5fdb9c@localhost>
On Thu, 9 May 2024, at 1:42 PM, William N. wrote:
> Regarding vmaps, I found that this syntax works:
>
> icmpv6 type . icmpv6 code . ip6 saddr . ip6 daddr . ct state vmap {
> 1 . 1 . ::/0 . ::/0 . established : continue
> }
>
> However, just like with sets, this does not work:
>
> icmpv6 type . icmpv6 code . ip6 saddr . ip6 daddr . ct state vmap {
> 1 . 1 . ::/0 . @ONE . established : continue
> }
>
> Is there really no way to refer to a set from within a concatenation/map?
I have yet to read the original question(s) that you sent to the list but I think the answer is that there is not.
--
Kerin Millar
next prev parent reply other threads:[~2024-05-09 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-05 19:25 Sets nesting/reference? Complex concatenations in vmaps? William N.
2024-05-09 12:42 ` William N.
2024-05-09 12:54 ` Kerin Millar [this message]
2024-05-09 13:15 ` William N.
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=dd5723aa-6516-4cfc-9a24-bc3e599dda54@app.fastmail.com \
--to=kfm@plushkava.net \
--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 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).