From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Marco d'Itri <md@Linux.IT>
Cc: netfilter@vger.kernel.org
Subject: Re: conntrackd and CacheWriteThrough
Date: Tue, 04 Nov 2008 19:58:15 +0100 [thread overview]
Message-ID: <49109B47.30802@netfilter.org> (raw)
In-Reply-To: <20081104160920.GA18489@bongo.bofh.it>
Marco d'Itri wrote:
> On Nov 04, Pablo Neira Ayuso <pablo@netfilter.org> wrote:
>
>> Sorry, this setup is no longer supported. At least until we find a sane
>> way to do it. See http://conntrack-tools.netfilter.org/manual.html.
>> Also see: http://marc.info/?l=netfilter&m=122164806109759&w=2
> Indeed I wondered about races between the traffic and state updates.
>
> Load sharing with a multicast MAC address and sources hashing would not
> help me because each one of my firewalls is connected to two core
> routers with no shared L2 domain between them (i.e. each router is
> connected to both firewalls).
>
> My real goal is not sharing load but supporting asymmetrical routing,
> because the firewalls announce the customer network to the core using
> an IGP. If I am not missing anything I could use OSPF and give a lower
> cost to the port with the higher VRRP priority.
> This way I would be able to use normal active/passive conntrack
> replication.
If this can guarantee that only one firewall filters all the traffic or
that the packets follow a symmetrical path in the filtering, that should
be fine.
BTW, I'd appreciate if you send me a couple of lines describing how to
do that so that I can add it to the user manual. I get an email about
OSPF/multi-path routing issues and conntrackd working once a month (at
least), others will appreciate if we can document all possible solutions
in this setup.
--
"Los honestos son inadaptados sociales" -- Les Luthiers
prev parent reply other threads:[~2008-11-04 18:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 15:53 conntrackd and CacheWriteThrough Marco d'Itri
2008-11-04 10:13 ` Pablo Neira Ayuso
2008-11-04 16:09 ` Marco d'Itri
2008-11-04 18:58 ` 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=49109B47.30802@netfilter.org \
--to=pablo@netfilter.org \
--cc=md@Linux.IT \
--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 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.