All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Serg <seentr@at.encryp.ch>
Cc: Eric <evil.function@proton.me>, netfilter@vger.kernel.org
Subject: Re: nftables: Internal error when checking rules
Date: Sun, 26 Mar 2023 22:45:37 +0200	[thread overview]
Message-ID: <ZCCu8ZQqwwWdyYwH@salvia> (raw)
In-Reply-To: <2041d22f-c06e-e81f-86f9-03f327711cd1@at.encryp.ch>

On Sun, Mar 26, 2023 at 07:17:48PM +0300, Serg wrote:
> Eric, thank you a lot! Your suggestion solved my issue.
> 
> For anyone interested, I will describe this situation in more details.
> 
> My nftables configuration consists of the main file (basically, it contains
> all logic and then includes child files which contain only single set per
> each). Set-files are written as follows:
> table netdev filter {
> 	set mySet {
> 		typeof ip saddr
> 		flags interval
> 		elements = { lots-of-entries-here, ...,
>                              i-had-913-entries-when-problem-happened }
> 	}
> }
> 
> As were mentioned by Eric, to workaround this issue all you need is to
> create "smaller 'add' pieces". Given that, we will have set-files look like
> this:
> add element netdev filter mySet { lots-of-entries-here }
> ...
> add element netdev filter mySet { i-had-913-entries-when-problem-happened }
> 
> Also you might want to add this line to the beginning of the file to ensure
> your set will be clean from removed entries (i.e. after set file was
> regenerated by a 3rd party script):
> flush set netdev filter mySet

You do not have to split your elements in individual commands.

Could you post some example reproducer? It would be also good to try
with lastest nftables version.

  reply	other threads:[~2023-03-26 20:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-26  9:46 nftables: Internal error when checking rules Serg
2023-03-26 15:18 ` Eric
2023-03-26 16:17   ` Serg
2023-03-26 20:45     ` Pablo Neira Ayuso [this message]
2023-03-26 20:48 ` Pablo Neira Ayuso
2023-03-27  9:10   ` Serg
2023-03-27 15:05     ` Pablo Neira Ayuso
2023-03-27 15:33       ` Serg

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=ZCCu8ZQqwwWdyYwH@salvia \
    --to=pablo@netfilter.org \
    --cc=evil.function@proton.me \
    --cc=netfilter@vger.kernel.org \
    --cc=seentr@at.encryp.ch \
    /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.