From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: Martin Kraus <lists_mk@wujiman.net>,
netfilter-devel@vger.kernel.org, netfilter@vger.kernel.org
Subject: Re: conntrackd, internal cache keeps filling up
Date: Tue, 13 May 2014 14:55:09 +0200 [thread overview]
Message-ID: <20140513125509.GA3881@localhost> (raw)
In-Reply-To: <20140513120400.GA22929@breakpoint.cc>
On Tue, May 13, 2014 at 02:04:00PM +0200, Florian Westphal wrote:
> Martin Kraus <lists_mk@wujiman.net> wrote:
> > On Mon, May 12, 2014 at 06:35:38PM +0200, Pablo Neira Ayuso wrote:
> > > > current kernel is 3.13.7.
> > > >
> > > > we already hit a bug in the official 3.2 kernel packaged with wheezy where
> > > > our scan for heartbleed vulnerability would cause conntrackd to kernel panic
> > > > the router.
> > >
> > > Please, provide more information on how to reproduce the problem that
> > > you're noticing. Thank you.
> >
> > regarding the kernel panic on 3.2 a colleague of mine was using nmap with it's
> > heartbleed plugin
> >
> > nmap --script ssl-heartbleed -sT -oX logfile.log 10.0.0.0/20
> >
> > http://nmap.org/nsedoc/scripts/ssl-heartbleed.html
> >
> > it took about 30 minutes to trigger the problem.
> [..]
>
> > NetlinkEventsReliable On
>
> known broken until at least Linux 3.6, see f.e.
>
> 5b423f6a40a0327f9d40bc8b97ce9be266f74368
> ("netfilter: nf_conntrack: fix racy timer handling with reliable events")
If they are using latest 3.2, that patch is already there.
next prev parent reply other threads:[~2014-05-13 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140505104058.GA30297@finrod>
[not found] ` <20140509113129.GA8031@localhost>
[not found] ` <20140510061743.GA32197@finrod>
2014-05-12 16:35 ` conntrackd, internal cache keeps filling up Pablo Neira Ayuso
2014-05-13 11:45 ` Martin Kraus
2014-05-13 12:04 ` Florian Westphal
2014-05-13 12:55 ` Pablo Neira Ayuso [this message]
2014-05-13 12:40 ` Pablo Neira Ayuso
2014-05-13 14:57 ` Martin Kraus
2014-07-11 16:27 ` Martin Kraus
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=20140513125509.GA3881@localhost \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=lists_mk@wujiman.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@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;
as well as URLs for NNTP newsgroup(s).