From: Francisco Pereira <fpereira@lojan.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] failover strategies - failing open vs. failing closed.
Date: Tue, 28 Dec 2004 17:01:14 +0000 [thread overview]
Message-ID: <1104256972.41d19fccd6e01@webmail.montevideo.com.uy> (raw)
In-Reply-To: <292B2D5F863ED611BB8B0008021089550315970E@aux.uwm.edu>
Mensaje citado por Kelly Jeglum <Jeglum@AUX.UWM.EDU>:
> I'd like to setup a box with 2 NICs as a firewall which will also rate
> limits outbound traffic. What happens when/if that box hangs or is
> rebooted?
>
> I'd like a solution that when there is a failure, traffic can still go
> through the box even though the firewall and rate limiting functions will no
> longer be in effect.
>
Maybe it is more than what you need, but did you know Virtual Router Redundancy
Protocol?
http://ftp.ietf.org/rfc/rfc2338.txt
There are several linux implementations.
> I believe that this is "failing closed" but have yet to find an intuitive
> definition - "closed" to traffic going through or (the opposite of an "open"
> circuit) a "closed" circuit which would allow traffic?
>
-------------------------------------------------------------
La Tienda del Portal esta de fiesta!
http://tienda.montevideo.com.uy
-------------------------------------------------------------
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-12-28 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 13:29 [LARTC] failover strategies - failing open vs. failing closed Kelly Jeglum
2004-12-28 14:50 ` Amit Vyas
2004-12-28 17:01 ` Francisco Pereira [this message]
2004-12-28 19:28 ` Stef Coene
2005-01-06 22:16 ` Jose Luis Araujo
2005-01-10 17:49 ` Yaman Saqqa
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=1104256972.41d19fccd6e01@webmail.montevideo.com.uy \
--to=fpereira@lojan.com \
--cc=lartc@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