All of lore.kernel.org
 help / color / mirror / Atom feed
From: <imnozi@gmail.com>
To: netfilter-devel@vger.kernel.org
Subject: Re: [nftables/nft] nft equivalent of "ipset test"
Date: Tue, 17 Oct 2023 20:00:57 -0400	[thread overview]
Message-ID: <20231017200057.57cfce21@playground> (raw)
In-Reply-To: <652F0C75.8010006@mutluit.com>

On Wed, 18 Oct 2023 00:36:37 +0200
"U.Mutlu" <um@mutluit.com> wrote:

> ...
> Actualy I need to do this monster:   :-)
> 
> IP="1.2.3.4"
> ! nft "get element inet mytable myset  { $IP }" > /dev/null 2>&1 && \
> ! nft "get element inet mytable myset2 { $IP }" > /dev/null 2>&1 && \
>    nft "add element inet mytable myset  { $IP }"

Try using '||', akin to:

----
mkdir aaaa; cd aaaa
touch a b

(
  ls a || \
  ls b
) >/dev/null 2>&1 || \
echo "not found"

(
  ls c || \
  ls b
) >/dev/null 2>&1 || \
echo "not found"

(
  ls a || \
  ls d
) >/dev/null 2>&1 || \
echo "not found"

(
  ls c || \
  ls d
) >/dev/null 2>&1 || \
echo "not found"

cd ..
rm -rf aaaa
----

Only if neither file is found will the echo execute.

So this should do the trick for you:

----
(
    nft "get element inet mytable myset  { $IP }" || \
    nft "get element inet mytable myset2 { $IP }"
) >/dev/null 2>&1 || \
  nft "add element inet mytable myset  { $IP }"
----

N

  reply	other threads:[~2023-10-18  0:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17 17:11 [nftables/nft] nft equivalent of "ipset test" U.Mutlu
2023-10-17 21:35 ` Florian Westphal
2023-10-17 21:55   ` U.Mutlu
2023-10-17 22:05     ` Florian Westphal
2023-10-17 22:36       ` U.Mutlu
2023-10-18  0:00         ` imnozi [this message]
2023-10-18  9:36           ` Pablo Neira Ayuso
2023-10-18  9:54             ` U.Mutlu
2023-10-18 10:00               ` Pablo Neira Ayuso
2023-10-18 11:07                 ` U.Mutlu
2023-10-18 11:49                   ` Pablo Neira Ayuso
2023-10-18 13:03                     ` U.Mutlu
2023-10-18 14:37                   ` Phil Sutter
2023-10-18 11:54               ` Kerin Millar
2023-10-18  9:23         ` Pablo Neira Ayuso

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=20231017200057.57cfce21@playground \
    --to=imnozi@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 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.