All of lore.kernel.org
 help / color / mirror / Atom feed
From: Piotrek Kaczmarek <kaczorek@k.daleka.net>
To: netfilter@lists.netfilter.org
Subject: Re: conntrack error
Date: Fri, 11 Feb 2005 17:32:14 +0100	[thread overview]
Message-ID: <20050211163214.GA18236@daleka.net> (raw)
In-Reply-To: <20050211153322.GA2516@bender.817west.com>

On Fri, Feb 11, 2005 at 03:33:22PM +0000, Jason Opperisano wrote:
> 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?

Yes, I set it by hand, I have 256mb of ram, currently there are ~17000 connections
and 'free' shows 70mb of free memory. That machine is dedicated to routing/firewalling

-- 
Piotr Kaczmarek


  reply	other threads:[~2005-02-11 16:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-11 10:55 conntrack error Piotrek Kaczmarek
2005-02-11 13:07 ` Jason Opperisano
2005-02-11 15:22   ` Piotrek Kaczmarek
2005-02-11 15:33     ` Jason Opperisano
2005-02-11 16:32       ` Piotrek Kaczmarek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-12 11:03 Piotrek Kaczmarek
2005-02-12 23:21 ` Patrick McHardy
2005-02-14 12:52   ` Rimas
2005-02-14 13:10     ` Patrick McHardy
2005-02-14 13:24       ` Rimas
2005-02-14 14:01       ` Rimas

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=20050211163214.GA18236@daleka.net \
    --to=kaczorek@k.daleka.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 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.