From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Roman Fiedler <roman.fiedler@ait.ac.at>
Cc: netfilter@vger.kernel.org
Subject: Re: Understanding conntrack: Delete and manual readd of same entry possible?
Date: Tue, 29 Dec 2009 21:06:58 +0100 [thread overview]
Message-ID: <4B3A6162.90003@netfilter.org> (raw)
In-Reply-To: <4B3A3F16.6060005@netfilter.org>
Pablo Neira Ayuso wrote:
> Roman Fiedler wrote:
>> Thanks for the patch. When I've played with the same problem at home I've
>> guessed that it is something with sequence numbers and that setting
>> tcp-liberal
>> in a netlink test application is a workaround for the DROP. But I did not
>> bring it to that point that I could create a clean patch because there
>> were
>> still some loose ends. Perhaps someone could help me to fix some of
>> these:
>>
>> a) When conntrackd inserts the entries, does it set the liberal also?
>> If yes,
>> is it correct, that a failover via conntrackd would disable sequence
>> number
>> tracking for all existing entries?
>
> Yes, this is the way it works by now, but it would be easy to make a
> patch not to disable it. I'm going to prepare one now that
> conntrack-tools 0.9.14 is out. I'll let you know, you may want to help
> me doing some testing.
BTW, conntrackd does not set to liberal other entries that already
exists in the kernel (in case that you have some active-active setup).
So only the injected entries are set to liberal by now. I think that
this replies to the second part of your question, right?
prev parent reply other threads:[~2009-12-29 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 7:55 Understanding conntrack: Delete and manual readd of same entry possible? Roman Fiedler
2009-12-23 23:05 ` Pablo Neira Ayuso
2009-12-29 10:42 ` Roman Fiedler
2009-12-29 17:40 ` Pablo Neira Ayuso
2009-12-29 20:06 ` Pablo Neira Ayuso [this message]
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=4B3A6162.90003@netfilter.org \
--to=pablo@netfilter.org \
--cc=netfilter@vger.kernel.org \
--cc=roman.fiedler@ait.ac.at \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.