All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Krzysztof Oledzki <olenf@ans.pl>
Cc: Harald Welte <laforge@netfilter.org>,
	Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>,
	Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [PATCH 2/3][CONNTRACK] Introduce the pickup facilities to take over TCP connections
Date: Tue, 22 Aug 2006 01:12:48 +0200	[thread overview]
Message-ID: <44EA3DF0.9040104@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0608212359410.3014@bizon.gios.gov.pl>

Krzysztof Oledzki wrote:
> On Mon, 21 Aug 2006, Pablo Neira Ayuso wrote:
> 
>> You seem to be confused with the IPS_PICKUP flag: this flag must be
>> set for conntracks created from userspace via ctnetlink, thus the TCP
>> window tracking knows that it has to take over the valid window of TCP
>> sequences, once that happens this flag is unset.
> 
> 
> Hm, lets assume we have two firewalls for active-active configuration.
> How does the second firewall know that it should accept/drop a packet
> with specific seq number from connection that was previously handled by
> the first one?
> 
> Plase excuse me if this is obvious, but I wasn't able to find any
> information about how it was solved. All I found is the TODO file
> with:
> 
> o support for TCP window tracking
>         - at the moment you have to disable it:
>         echo 1 > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_be_liberal


I think the question is whether connections will bounce between nodes
multiple times or just once when a node fail. The former would need
to have the IPS_PICKUP flag constantly enabled.

  reply	other threads:[~2006-08-21 23:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-21  8:46 [PATCH 2/3][CONNTRACK] Introduce the pickup facilities to take over TCP connections Pablo Neira Ayuso
2006-08-21 10:18 ` Krzysztof Oledzki
2006-08-21 20:04   ` Pablo Neira Ayuso
2006-08-21 22:15     ` Krzysztof Oledzki
2006-08-21 23:12       ` Patrick McHardy [this message]
2006-09-24  3:46         ` 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=44EA3DF0.9040104@trash.net \
    --to=kaber@trash.net \
    --cc=laforge@netfilter.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=olenf@ans.pl \
    --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.