From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Subject: Re: [PATCH 1/4][CONNTRACK] Introduce flag facilities to take over TCP connections
Date: Thu, 23 Nov 2006 14:28:09 +0100 [thread overview]
Message-ID: <4565A1E9.4060802@trash.net> (raw)
In-Reply-To: <4553D2F2.1020107@netfilter.org>
Pablo Neira Ayuso wrote:
> This patch introduces two new flags called IPS_PICKUP that forces the
> protocol handler to pick up the window of valid TCP packets and
> IPS_IN_WINDOW to by pass window checkings.
>
> Moreover, four new attributes to inject the window scale factor and
> enable SACK are introduced. These new facilities provide the appropiate
> mechanisms to take over TCP connections in failover settings with TCP
> tracking enabled.
I still think a simple flag/mask attribute would be nicer and
would save lots of code. The TCP flag values are already exposed
to userspace. Something like:
CTA_PROTOINFO_TCP_FLAGS_ORIGINAL:
struct tcp_flags {
u_int32_t flags;
u_int32_t mask;
};
ct->proto.tcp.seen[].flags &= ~attr->mask;
ct->proto.tcp.seen[].flags |= attr->flags & attr->mask;
Even better might be to nest all directional attributes under
a CTA_ORIGNAL/CTA_REPLY attribute.
prev parent reply other threads:[~2006-11-23 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 1:16 [PATCH 1/4][CONNTRACK] Introduce flag facilities to take over TCP connections Pablo Neira Ayuso
2006-11-10 20:49 ` Jozsef Kadlecsik
2006-11-12 19:03 ` Pablo Neira Ayuso
2006-11-23 13:28 ` Patrick McHardy [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=4565A1E9.4060802@trash.net \
--to=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@lists.netfilter.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 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.