Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: Mike Dillinger <miked@softtalker.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>, netfilter@vger.kernel.org
Subject: Re: nftables: Strange Error When Adding Element to Named Set
Date: Tue, 2 Jun 2020 16:25:36 +0200	[thread overview]
Message-ID: <20200602162536.55948b65@redhat.com> (raw)
In-Reply-To: <29f39abf-a146-fa5a-6178-574cbfb9c83c@softtalker.com>

Hi Mik,

On Tue, 2 Jun 2020 06:28:31 -0700
Mike Dillinger <miked@softtalker.com> wrote:

> > *From:* Mike Dillinger [mailto:miked@softtalker.com]
> > *To:* Pablo Neira Ayuso <pablo@netfilter.org>
> > *Cc:* netfilter@vger.kernel.org, sbrivio@redhat.com
> > *Date:* Monday, June 1, 2020, 9:07 AM PDT
> > *Subject:* nftables: Strange Error When Adding Element to Named Set
> >
> > Yes, I have found a way to reproduce it.
> >
> > Add the set:
> > nft add set ip filter blacklist4-ip-1m {type ipv4_addr\; flags
> > interval,timeout \; timeout 1m \; gc-interval 1m\;}
> >
> > We're not concerned about the IP's that are added to the set
> > because there are no rules covering what to do with the set
> > contents.
> >
> > I wrote a bash script called nftables-bug-repro:
> > #!/bin/bash
> > nft list set ip filter blacklist4-ip-1m
> > for ((i=1;i<=10;i++)); do
> >     nft add element filter blacklist4-ip-1m {$i.$i.$i.$i}
> >     sleep 1
> > done
> > nft list set ip filter blacklist4-ip-1m  
> 
> Hi Pablo, Stefan, et al,
> 
> I wanted to check and see if anyone was able to reproduce the issue.Â
>  If not, I'd like to figure out what's unique about my setup so I can
> resolve the issue on my end.

I haven't tried yet. I plan to check later today, I'll let you know. I
don't think there's anything unique about your setup.

-- 
Stefano


  reply	other threads:[~2020-06-02 14:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08 14:06 nftables: Strange Error When Adding Element to Named Set Mike Dillinger
2020-05-08 16:01 ` Pablo Neira Ayuso
2020-05-08 17:13   ` Mike Dillinger
2020-05-31 17:18   ` Mike Dillinger
2020-06-01 12:41     ` Pablo Neira Ayuso
2020-06-01 14:58       ` Mike Dillinger
2020-06-01 15:48         ` Stefano Brivio
2020-06-01 16:13           ` Mike Dillinger
2020-06-01 16:07         ` Mike Dillinger
2020-06-02 13:28           ` Mike Dillinger
2020-06-02 14:25             ` Stefano Brivio [this message]
2020-06-02 16:38               ` Stefano Brivio
2020-06-02 19:58                 ` Mike Dillinger
2020-06-06 13:10                   ` meta day not working pauloric
2020-06-06 14:37                     ` Florian Westphal
2020-06-06 15:06                       ` pauloric

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=20200602162536.55948b65@redhat.com \
    --to=sbrivio@redhat.com \
    --cc=miked@softtalker.com \
    --cc=netfilter@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