public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: safemode <safemode@voicenet.com>
To: linux-kernel@vger.kernel.org
Subject: (iptables) ip_conntrack bug?
Date: Wed, 15 Nov 2000 15:46:03 -0500	[thread overview]
Message-ID: <20001115154603.D4089@psuedomode> (raw)

I was DDoS'd today while away and came home to find the firewall unable to
do anything network related (although my connection to irc was still
working oddly).  a quick dmesg showed the problem.
ip_conntrack: maximum limit of 2048 entries exceeded
NET: 1 messages suppressed.
ip_conntrack: maximum limit of 2048 entries exceeded
NET: 3 messages suppressed.
ip_conntrack: maximum limit of 2048 entries exceeded
NAT: 0 dropping untracked packet c1e69980 6 192.168.1.2 -> 206.251.7.30
ip_conntrack: maximum limit of 2048 entries exceeded
NAT: 0 dropping untracked packet c1e69b60 6 192.168.1.2 -> 206.251.7.30
ip_conntrack: maximum limit of 2048 entries exceeded


That is a very small snippet of dmesg.  It seems that ip_conntrack did not
flush or reset after the attack, even though everything was fine when i got
home.  Keep in mind, this was a somewhat massive attack on my network here
but is only connected via a DSL line, it seems the attackers sent hundreds
or thousands of very small packets resulting in 21000 connection attempts
in a short amount of time.  Is this a bug with ip_conntrack?  this is
kernel version 2.4.0-test5, it's been up for 74 days.  I had to reload
ip_conntrack to flush it and everything worked fine after that.    Thanks
for any info.  

ps.  If this is a previously discovered bug, is it fixed in the latest
kernels?

-
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/

             reply	other threads:[~2000-11-15 21:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-15 20:46 safemode [this message]
2000-11-15 21:19 ` (iptables) ip_conntrack bug? Guus Sliepen
2000-11-15 21:34   ` safemode
2000-11-15 22:54     ` Guus Sliepen
2000-11-15 23:03   ` Dan Aloni
2000-11-15 23:42     ` Dan Aloni
2000-11-16  0:00       ` Dan Aloni
2000-11-17  2:50       ` Rusty Russell
2000-11-17  2:01 ` Rusty Russell
  -- strict thread matches above, loose matches on Subject: below --
2000-11-15 23:47 Samium Gromoff

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=20001115154603.D4089@psuedomode \
    --to=safemode@voicenet.com \
    --cc=linux-kernel@vger.kernel.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