From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "Humberto Jucá" <betolj@gmail.com>
Cc: Arnoud Tijssen <ATijssen@ram.nl>, netfilter@vger.kernel.org
Subject: Re: About cluster deployments.
Date: Thu, 13 Dec 2012 12:12:49 +0100 [thread overview]
Message-ID: <20121213111249.GA23251@1984> (raw)
In-Reply-To: <CACuyg25y_0DHZumvdLUY0455t+AJeckNkYKmCmZj747C3S1vqg@mail.gmail.com>
Hi Humberto,
On Tue, Dec 11, 2012 at 07:19:36AM -0300, Humberto Jucá wrote:
> Hi, thanks for response!
>
> But I like to known what were your experiences.
>
> You already made active/active configurations?
> How you handled the traffic to the two firewalls?
> Worked with multicast arp or port mirroring?
For active/active firewalls/gatewyas, you will have to use arptables +
the cluster match. The CLUSTERIP target is designed to only work for
backend servers.
next prev parent reply other threads:[~2012-12-13 11:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 16:27 About cluster deployments Humberto Jucá
2012-12-10 6:21 ` Arnoud Tijssen
2012-12-11 10:19 ` Humberto Jucá
2012-12-11 10:28 ` Arnoud Tijssen
2012-12-13 11:12 ` Pablo Neira Ayuso [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-12-07 16:21 Humberto Jucá
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=20121213111249.GA23251@1984 \
--to=pablo@netfilter.org \
--cc=ATijssen@ram.nl \
--cc=betolj@gmail.com \
--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 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).