From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Edison Figueira <efjgrub@gmail.com>, netfilter@vger.kernel.org
Subject: Re: CLUSTERIP: no conntrack error
Date: Mon, 26 Jul 2010 13:09:15 +0200 [thread overview]
Message-ID: <4C4D6CDB.2060900@netfilter.org> (raw)
In-Reply-To: <alpine.LSU.2.01.1007261300020.323@obet.zrqbmnf.qr>
On 26/07/10 13:00, Jan Engelhardt wrote:
> On Monday 2010-07-26 12:35, Pablo Neira Ayuso wrote:
>> On 25/07/10 18:34, Jan Engelhardt wrote:
>>> On Wednesday 2010-07-14 00:18, Edison Figueira wrote:
>>>
>>>> I configured CLUSTERIP in two boxes to make balancing proxy, and
>>>> apparently it all worked but I get several messages from "CLUSTERIP:
>>>> no conntrack.
>>>>
>>>> Does anyone know what this message means?
>>>
>>> Means packets are tagged as INVALID.
>>
>> Indeed. You have to add a rule to drop invalid packets before the CLUSTERIP
>> rule to avoid this message.
>
> Hm, couldn't we just drop the message? There are many other components
> in Netfilter that silently bail out when nf_ct_get returns NULL, like
> xt_connlimit.
Yes, it's a good idea for the short run.
In the long run, we should deprecate CLUSTERIP since it has been
superseded by the cluster match. However, I wanted to document the new
approach before doing so (I found no spare time to do it).
IIRC, the message is only displayed if netfilter debugging is enabled.
next prev parent reply other threads:[~2010-07-26 11:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 22:18 CLUSTERIP: no conntrack error Edison Figueira
2010-07-25 16:34 ` Jan Engelhardt
2010-07-26 10:35 ` Pablo Neira Ayuso
2010-07-26 11:00 ` Jan Engelhardt
2010-07-26 11:09 ` Pablo Neira Ayuso [this message]
2010-07-26 11:13 ` Jan Engelhardt
2010-07-26 13:43 ` Edison Figueira
2010-07-26 17:05 ` Pablo Neira Ayuso
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=4C4D6CDB.2060900@netfilter.org \
--to=pablo@netfilter.org \
--cc=efjgrub@gmail.com \
--cc=jengelh@medozas.de \
--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