From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Opperisano Subject: Re: conntrack error Date: Fri, 11 Feb 2005 10:33:22 -0500 Message-ID: <20050211153322.GA2516@bender.817west.com> References: <20050211105519.GA14110@daleka.net> <1108127256.4489.27.camel@hubcap.ljm.dom> <20050211152217.GA17270@daleka.net> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <20050211152217.GA17270@daleka.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-bounces@lists.netfilter.org Errors-To: netfilter-bounces@lists.netfilter.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: netfilter@lists.netfilter.org On Fri, Feb 11, 2005 at 04:22:17PM +0100, Piotrek Kaczmarek wrote: > # sysctl net.ipv4.netfilter.ip_conntrack_max > net.ipv4.netfilter.ip_conntrack_max = 30000 i assume you set that manually, as i don't think there's an amount of physical RAM that would result in 30000 on the dot... speaking of which--how much physical RAM does this machine have? you would need 512 MB RAM for ip_conntrack_max to be automatically calculated to 32768, even though the conntrack table would only really use around 12 MB of kernel memory. also--is this machine dedicated solely to firewalling, or is there something else chewing up your RAM? -j -- "I have thought this through. First, I will send Bart the money to fly home. Then I will murder him." --The Simpsons