From: "Jet" <yenjet.chan@eglobal.com.my>
To: mail@vickysh.wlink.com.np, Maciej Soltysiak <solt@dns.toxicfilms.tv>
Cc: netfilter@lists.samba.org
Subject: Re: ip_conntrack: table full, dropping packet.
Date: Fri, 1 Nov 2002 10:02:37 +0800 [thread overview]
Message-ID: <00ad01c2814a$c107c4b0$0bc8c80a@dolphin> (raw)
In-Reply-To: 200210311225.47844.mail@vickysh.wlink.com.np
No I guess the maximum value is 64K.
Yes. It did crash my machine.
Just FYI, I tried this before on my 64M RAM linux box.
The default is 4K connection max.
But I tried to increase it to 64K.
End up when the number of connections grow to 13K (based on
/proc/net/ip_conntrack),
it first starts killing my other processes including klogd, syslog-ng,
snort.
At this time, you can see the kernel start killing the process from your
syslog (before syslog died)
After a while my linux box hang. And wait for reboot
I guess this is related to OOM (out-of-memory) bug in the kernel (I'm using
2.4.18-xfs).
.//Jet
>
> If I increase the value what negative effect does it have??? Can I
increase it
> to say 3276800 ???? Hope It doesnot crash my machine.
>
>
next prev parent reply other threads:[~2002-11-01 2:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 13:43 ip_conntrack: table full, dropping packet Vicky Shrestha
2002-10-30 16:28 ` Antony Stone
2002-10-30 16:59 ` Maciej Soltysiak
2002-10-31 6:40 ` Vicky Shrestha
2002-11-01 2:02 ` Jet [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-19 21:35 Strange setup Evan Borgstrom
2003-01-19 22:31 ` Peter Johnson
2003-01-20 0:45 ` Evan Borgstrom
2003-01-20 7:50 ` Peter Johnson
2003-01-20 14:49 ` Evan Borgstrom
2003-01-20 15:01 ` ip_conntrack: table full, dropping packet hare ram
2003-01-20 15:13 ` Maciej Soltysiak
2004-09-24 4:01 www.piratehosting.net
2004-09-24 7:02 ` Jason Opperisano
2004-09-26 20:34 ` Jose Maria Lopez
2004-09-24 8:07 www.piratehosting.net
2004-09-24 15:19 ` Stephen J Smoogen
2004-09-24 15:55 www.piratehosting.net
2004-09-26 20:34 ` Jose Maria Lopez
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='00ad01c2814a$c107c4b0$0bc8c80a@dolphin' \
--to=yenjet.chan@eglobal.com.my \
--cc=mail@vickysh.wlink.com.np \
--cc=netfilter@lists.samba.org \
--cc=solt@dns.toxicfilms.tv \
/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