All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kamil Jońca" <kjonca@op.pl>
To: netfilter@vger.kernel.org
Subject: Re: exclude named sets
Date: Fri, 20 May 2022 11:10:45 +0200	[thread overview]
Message-ID: <87tu9kh8mi.fsf@alfa.kjonca> (raw)
In-Reply-To: <CAMsxNkTfGW+dhr32RYFxn1rdJDRCSBFms_fJa5UVhPb-Piad-w@mail.gmail.com> (Andrew Clark's message of "Fri, 20 May 2022 12:01:31 +0300")

Andrew Clark <andrewclarkii@gmail.com> writes:

> Thank you for your answer Kamil!
> Under words "not valid" I mean this:
>
> root@anvil:~# /usr/sbin/nft -f /etc/nftables.conf
> /etc/nftables.conf:113:48-48: Error: syntax error, unexpected @
>                 iifname $int_ifs ip daddr != { @stormwall, @akamai }
> meta l4proto tcp redirect to :9051
>                                                ^
And that is what I expected.

> root@anvil:~# vim /etc/nftables.conf
> root@anvil:~# /usr/sbin/nft -f /etc/nftables.conf
> /etc/nftables.conf:113:49-57: Error: unknown identifier 'stormwall'
>                 iifname $int_ifs ip daddr != { $stormwall, $akamai }
> meta l4proto tcp redirect to :9051
>                                                 ^^^^^^^^^
> Your proposal:
>
> iifname $int_ifs ip daddr != @akamai meta l4proto tcp redirect to :9051
>
> Also does not work.
And error message is ... ?
How you define these sets?
by
--8<---------------cut here---------------start------------->8---
define SIMPLE_SET = ...
--8<---------------cut here---------------end--------------->8---
or  as named set?

KJ

-- 
http://stopstopnop.pl/stop_stopnop.pl_o_nas.html

  reply	other threads:[~2022-05-20  9:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20  9:01 exclude named sets Andrew Clark
2022-05-20  9:10 ` Kamil Jońca [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-05-20 11:04 Andrew Clark
2022-05-30  8:10 ` Robert Sander
2022-05-20  3:49 Andrew Clark
2022-05-20  4:32 ` Kamil Jońca
2022-05-20 10:57 ` Benno

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=87tu9kh8mi.fsf@alfa.kjonca \
    --to=kjonca@op.pl \
    --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.