From: Rusty Russell <rusty@linuxcare.com.au>
To: rtviado <root@iligan.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ip_conntrack: maximum limit of 16368 entries exceeded
Date: Wed, 17 Jan 2001 13:13:28 +1100 [thread overview]
Message-ID: <E14Ii6K-00014V-00@halfway> (raw)
In-Reply-To: Your message of "Tue, 16 Jan 2001 14:48:40 +0800." <Pine.LNX.4.30.0101161444450.24215-100000@bigbird-ipgi.iligan.com>
In message <Pine.LNX.4.30.0101161444450.24215-100000@bigbird-ipgi.iligan.com> y
ou write:
> I got this in my logs:
>
> ip_conntrack: maximum limit of 16368 entries exceeded
It's OK, it just means that you have *alot* of connections going
through your box (or maybe you don't route both ways through your box,
which you need to do for connection tracking to work). We have to be
slow in timing out connections, but when the limit gets hit, we get
more aggressive: the algo's pretty good, so you probably won't notice
any problems.
Cheers,
Rusty.
--
http://linux.conf.au The Linux conference Australia needed.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-19 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 6:48 ip_conntrack: maximum limit of 16368 entries exceeded rtviado
2001-01-16 13:44 ` Sven Koch
2001-01-17 2:13 ` Rusty Russell [this message]
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=E14Ii6K-00014V-00@halfway \
--to=rusty@linuxcare.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=root@iligan.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox