From: Phil Oester <kernel@linuxace.com>
To: Thomas Jarosch <thomas.jarosch@intra2net.com>
Cc: netfilter-devel <netfilter-devel@lists.netfilter.org>
Subject: Re: ip_conntrack table full problem
Date: Mon, 21 Mar 2005 13:14:41 -0800 [thread overview]
Message-ID: <20050321211441.GA15155@linuxace.com> (raw)
In-Reply-To: <200503211923.48964.thomas.jarosch@intra2net.com>
On Mon, Mar 21, 2005 at 07:23:48PM +0100, Thomas Jarosch wrote:
> > No easy way. Last week I posted a patch which would have made
> > this possible by creating a 'cleaned' list, but since you cannot
> > upgrade kernels, you could not use this anyway.
>
> But I can still patch kernels ;-)
OK, I'll send along a 2.4.21 -> 2.6.11 patch shortly ;-)
> IIRC the box makes heavy use of SNAT/DNAT for port forwarding.
> I'll try to get a copy of the firewall rules tomorrow and
> test it locally here.
>
> Is there an easy way to see if it leaked conntracks?
> Should the information in /proc/slabinfo be somewhat proportional
> to the number of connections/lines in /proc/net/ip_conntrack?
Yes, the numbers should be in the same ballpark. Conntracks are being
cleaned from the lists (i.e. /proc/net/ip_conntrack), but never being
destroyed. In my testing this is caused by a process not freeing
the skb. What kinds of processes are running on this box?
Phil
next prev parent reply other threads:[~2005-03-21 21:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 15:47 ip_conntrack table full problem Thomas Jarosch
2005-03-14 17:18 ` Phil Oester
2005-03-15 10:13 ` Thomas Jarosch
2005-03-21 14:13 ` Thomas Jarosch
2005-03-21 16:21 ` Phil Oester
2005-03-21 17:03 ` Thomas Jarosch
2005-03-21 18:08 ` Phil Oester
2005-03-21 18:23 ` Thomas Jarosch
2005-03-21 21:14 ` Phil Oester [this message]
2005-03-21 22:58 ` Thomas Jarosch
2005-03-21 18:41 ` Patrick Schaaf
2005-03-21 21:15 ` Phil Oester
2005-03-23 2:38 ` Patrick McHardy
2005-03-23 9:11 ` Thomas Jarosch
2005-03-29 20:26 ` Thomas Jarosch
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=20050321211441.GA15155@linuxace.com \
--to=kernel@linuxace.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=thomas.jarosch@intra2net.com \
/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.