From: Roman Fiedler <roman.fiedler@ait.ac.at>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter@vger.kernel.org
Subject: Re: Understanding conntrack: Delete and manual readd of same entry possible?
Date: Tue, 29 Dec 2009 11:42:05 +0100 [thread overview]
Message-ID: <4B39DCFD.8070808@ait.ac.at> (raw)
In-Reply-To: <4B32A248.9070403@netfilter.org>
Pablo Neira Ayuso wrote:
> Roman Fiedler wrote:
>> Hi list,
>>
>> The failure to conduct a simple test with conntrack makes me believe,
>> that I misunderstood some part of the concept.
>>
>> The testcase ....
>
> I seem to have overlooked this email, sorry. You need this patch in
> order to make it work, I'm going to apply it to git.netfilter.org now so
> it will be available in the next release.
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?
b) Does the netlink api support sequence number parameters? If not, should it?
c) If the sequence numbers are not set by the conntrack utility, where do the
values in the kernel space come from? Are they all 0 or is it uninitialized
memory from user or kernel space?
next prev parent reply other threads:[~2009-12-29 10:42 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 [this message]
2009-12-29 17:40 ` Pablo Neira Ayuso
2009-12-29 20:06 ` 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=4B39DCFD.8070808@ait.ac.at \
--to=roman.fiedler@ait.ac.at \
--cc=netfilter@vger.kernel.org \
--cc=pablo@netfilter.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).