Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Neal P. Murphy" <neal.p.murphy@alum.wpi.edu>
Cc: netfilter@vger.kernel.org
Subject: Re: Rule Count limit
Date: Thu, 24 Sep 2020 13:40:31 -0400	[thread overview]
Message-ID: <20200924134031.30856252@playground> (raw)
In-Reply-To: <CAKw0Lq2f1KbF34gTQyxYiZW8s1Neg-q0x1_FcE=qSrP9joWtqA@mail.gmail.com>

On Thu, 24 Sep 2020 16:17:00 +0530
Jevin Gala <jevin@softaculous.com> wrote:

> Hi,
> 
> 
> I couldn’t find much information about the limitation on adding number of rules.
> 
> I tried adding around 26000 rules and starting seeing this message :

6-8 years ago, I discovered that iptables could not reliably add more than 20k-25k rules at a time; a periodic COMMIT (IIRC) every 10k-15k rules would allow me to add hundreds of thousands of rules. So there is or was a limit to iptables' atomicity. Back then, I was comparing the efficiency of Smoothwall Express' ipbatch program and iptables-restore and needed a million rules to obtain meaningful data; ipbatch was marginally (~5%) more efficient.

N

> 
> 
> Unable to update the kernel. Two possible causes:
> 
> 1. Multiple ebtables programs were executing simultaneously. The ebtables
> 
>    userspace tool doesn't by default support multiple ebtables programs running
> 
>    concurrently. The ebtables option --concurrent or a tool like flock can be
> 
>    used to support concurrent scripts that update the ebtables kernel tables.
> 
> 2. The kernel doesn't support a certain ebtables extension, consider
> 
>    recompiling your kernel or insmod the extension.
> 
> 
> There is Free RAM while swap is fully used.
> 
> Kernel : 3.10.0-957.5.1.el7.x86_64
> 
> ebtables.x86_64 2.0.10-16.el7
> 
> 


      reply	other threads:[~2020-09-24 17:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-24 10:47 Rule Count limit Jevin Gala
2020-09-24 17:40 ` Neal P. Murphy [this message]

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=20200924134031.30856252@playground \
    --to=neal.p.murphy@alum.wpi.edu \
    --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