Linux Netfilter discussions
 help / color / mirror / Atom feed
From: px <px5150@yahoo.com>
To: netfilter@lists.netfilter.org
Cc: dom@fea.net
Subject: maximum number of iptables rules?
Date: Wed, 12 Nov 2003 15:18:12 -0800	[thread overview]
Message-ID: <3FB2BFB4.2000105@yahoo.com> (raw)

Hi, me and a buddy of mine are working on a perl script to automate 
blocking of about 3000 IP addresses.
The script works fine on his box, x86.  But on my box, sparc, I seem to 
have a limitation of 854 rules before I start to get errors and am 
unable to add anymore rules.
Is there a maximum number of rules per chain? or overall?
 

Here is the information on my Sparc box.

> null:~# iptables -t filter -I INPUT 1 -s 66.28.224.0/19 -p all -j blockme
> iptables: Memory allocation problem


> null:~# iptables -t filter -I INPUT 1 -s 1.2.3.4/19 -p all -j blockme
> iptables: Memory allocation problem
> null:~# uname -a
> Linux null 2.4.21 #1 Thu Aug 7 20:30:12 EDT 2003 sparc64 GNU/Linux
> null:~#

> null:~# iptables -L blockme
> Chain blockme(854 references)
> target     prot opt source               destination
> DROP       all  --  anywhere             anywhere


Here is the info about my buddy's. x86 box

>  root@darkside:/etc/rc.d# uname -a; iptables -L blockme; iptables 
> --version
>  Linux darkside 2.5.50-ac1 #3 SMP Sun Feb 9 10:21:53 PST 2003 i686 
> unknown
>  Chain blockme(3966 references)
>  target     prot opt source               destination          
>  DROP       all  --  anywhere             anywhere            
>  iptables v1.2.7a



Any help is greatly appreciated.
-r0b




             reply	other threads:[~2003-11-12 23:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-12 23:18 px [this message]
2003-11-12 23:25 ` maximum number of iptables rules? Antony Stone
  -- strict thread matches above, loose matches on Subject: below --
2003-11-12 23:40 px

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=3FB2BFB4.2000105@yahoo.com \
    --to=px5150@yahoo.com \
    --cc=dom@fea.net \
    --cc=netfilter@lists.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