mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guus Sliepen <guus@warande3094.warande.uu.nl>
To: netfilter@us5.samba.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: (iptables) ip_conntrack bug?
Date: Wed, 15 Nov 2000 23:54:34 +0100	[thread overview]
Message-ID: <20001115235433.M13682@sliepen.warande.net> (raw)
In-Reply-To: <20001115154603.D4089@psuedomode> <20001115221922.L13682@sliepen.warande.net> <20001115163450.E4089@psuedomode>
In-Reply-To: <20001115163450.E4089@psuedomode>; from safemode@voicenet.com on Wed, Nov 15, 2000 at 04:34:50PM -0500

[-- Attachment #1: Type: text/plain, Size: 1698 bytes --]

On Wed, Nov 15, 2000 at 04:34:50PM -0500, safemode wrote:

> On Wed, 15 Nov 2000 16:19:23 Guus Sliepen wrote:
> > On Wed, Nov 15, 2000 at 03:46:03PM -0500, safemode wrote:
> > 
> > > 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
> > [...]
> > 
> > I have also seen this happen on a box which ran test9. Apparently because
> > of
> > it's long uptime, because the logs should no signs of an attack.

safemode and I discussed this and we tried to find an answer in the kernel
source. However, the chain of called functions is too long to determine where
exactly the problem is. But most likely, because init_conntrack() can fail
(because it cannot free an entry, which is either because netfilter does not
dare to throw out entries with large timeouts (tcp connections have ridiculous
long timeouts btw, almost 2.3 days?!) or because IPS_CONFIRMED is not set), and
this failure is propagating back all the way to the tcp code, so that no new
sockets can be opened.

From our point of view, the conntrack stuff should be totally transparent to the
tcp/ip stack. Since this allows for a DoS attack, might be wise to fix this
before 2.4 comes out...

-------------------------------------------
Met vriendelijke groet / with kind regards,
  Guus Sliepen <guus@sliepen.warande.net>
-------------------------------------------
See also: http://tinc.nl.linux.org/
          http://www.kernelbench.org/
-------------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2000-11-15 23:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-15 20:46 safemode
2000-11-15 21:19 ` Guus Sliepen
2000-11-15 21:34   ` safemode
2000-11-15 22:54     ` Guus Sliepen [this message]
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
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=20001115235433.M13682@sliepen.warande.net \
    --to=guus@warande3094.warande.uu.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netfilter@us5.samba.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

all inboxes | Powered by JetHome®