From: Jakub Jakacki <admin@md4.pl>
To: netfilter@lists.netfilter.org
Subject: Re: filtering asym. routing without "ip_conntrack: table full"?
Date: Tue, 21 Jan 2003 11:45:05 +0100 [thread overview]
Message-ID: <20030121104505.GD603@mispa> (raw)
In-Reply-To: <20030121061614.GA24090@kwaak.net>
On Tue, Jan 21, 2003 at 07:16:15AM +0100, Ard van Breemen wrote:
> On Tue, Jan 14, 2003 at 10:37:11AM +0100, Christian Hammers wrote:
> > I have a border router that does dynamic and asymetric routing.
> > Now, after upgrading from 2.4.19 to 2.4.20 yesterday I got the following
> > message in my syslog twice this night:
> > kernel: ip_conntrack: table full, dropping packet.
> > The /proc/net/ip_conntrack table has 36911 entries, mostly all [UNREPLIED].
> Heh,
> Next to the other replies:
> If you do massive routing, or better: massive firewalling (a lot
> of connections going through), always load the ip_conntrack
> module with hashsize= .
> If you don't, most of the connections have to be sequentially
> searched in a linked list.
> Default max setting of hashsize is 8192, with a maximum of 58000
> connections being tracked. The maximum connections to be tracked
> can be increased on the fly, but upping your hashsize to begin
> with gives you certainly an extra performance boost.
> (Heh, it can make your cpu system time go from 100% down to 5 or
> so... At least it will make your ethernet driver be the bottle
> neck)
>
> --
> mail up 65+19:29, 4 users, load 0.00, 0.02, 0.27
> mistar1 up 18+15:59, 9 users, load 0.00, 0.00, 0.01
> Let your government know you value your freedom: sign the petition:
> http://petition.eurolinux.org
>
>
>
I have the same problem, and have found /proc/sys/net/ip_conntrack_max.
Is it contains the default max hashsize? May I only write:
cat 16384 > /proc/sys/net/ip_conntract_max
to solve the problem of "full table"?
Will it be the same as loading ip_conntrack module with hashsize= ?
Best regards
Jakub
next prev parent reply other threads:[~2003-01-21 10:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 9:37 filtering asym. routing without "ip_conntrack: table full"? Christian Hammers
2003-01-14 12:12 ` /proc/net/ip_conntrack filling without ipt_conntrack.o loaded? Christian Hammers
2003-01-14 13:43 ` Filip Sneppe
2003-01-14 15:06 ` Christian Hammers
2003-01-14 15:49 ` Filip Sneppe
2003-01-14 16:01 ` Christian Hammers
2003-01-14 16:09 ` Filip Sneppe
2003-01-14 16:37 ` Christian Hammers
2003-01-14 16:58 ` Filip Sneppe
2003-01-21 6:16 ` filtering asym. routing without "ip_conntrack: table full"? ard-netfilter
2003-01-21 10:45 ` Jakub Jakacki [this message]
2003-01-29 2:14 ` Arnt Karlsen
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=20030121104505.GD603@mispa \
--to=admin@md4.pl \
--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