From: Patrick McHardy <kaber@trash.net>
To: "Nesser, Phil" <nesser@amazon.com>
Cc: "netfilter-devel@lists.netfilter.org"
<netfilter-devel@lists.netfilter.org>
Subject: Re: rule limitations?
Date: Wed, 29 Aug 2007 20:53:15 +0200 [thread overview]
Message-ID: <46D5C09B.7000708@trash.net> (raw)
In-Reply-To: <4D25F22093241741BC1D0EEBC2DBB1DA365FFCDB@EX-SEA5-D.ant.amazon.com>
Nesser, Phil wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> For relatively obscure reasons, I am trying to build a set of rules that run into the hundreds of thousands. I was experimenting on a Redhat Release 5 machine with 2.6.18 kernel and 1.3.5 iptables. I was able to load around 340k rules before getting an error of iptables-restore: line XXXXXX failed.
>
> So I try it out on a server (much beefier, 8G ram, dual quad core 2GHz proc) running the same kernel/iptables versions. This time it died in the same way at about 40k rules. After some research I found a log message on Vmalloc failures, so I figured what the hell and rebuilt the server using the 64 bit version of RH 5. Now no more vmalloc failures, but still dies at around 40k entries.
>
> I am more than happy to build a custom kernel if that what I need to do. I have poked around the sources and it is not obvious what needs to change.
>
> Any help would be appreciated.
What error message do you get (or if its too unspecific, what does
strace show)?
next prev parent reply other threads:[~2007-08-29 18:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 23:48 rule limitations? Nesser, Phil
2007-08-29 18:53 ` Patrick McHardy [this message]
2007-09-02 7:43 ` Jesper Dangaard Brouer
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=46D5C09B.7000708@trash.net \
--to=kaber@trash.net \
--cc=nesser@amazon.com \
--cc=netfilter-devel@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 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.