From: sabat <sabat@eloan.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Redundant Routes to *Same* ISP
Date: Tue, 03 Dec 2002 18:52:23 +0000 [thread overview]
Message-ID: <marc-lartc-103895650511474@msgid-missing> (raw)
I've seen a lot of info about running redundant routes to different ISPs
in the HOWTO and on this list. That surprises me, because I would expect
that a more common situation would be redundant routes to the *same* ISP
-- the typical HSRP + load balancing that so many of them run. Here's
what I want to do:
====== ======
ISP Router 1 ---- HSRP ---- ISP Router 2
====== \ / ======
| \ / |
| / \ |
| / \ |
====== / \ ======
My Router 1 -- heartbeat -- My Router 2
(Linux) (Linux)
====== ======
| |
| |
====== ======
fw 1 fw 2
I'm thinking of running ECMP outgoing from the routers labeled "My
Router x" to the ISP routers. It's also probable that we'll have the
ISP's routers sending us alternating (ECMP) packets on the incoming
side. Our routers would have heartbeat running so that a failure on
either box would cause the surviving router to take over its IP and MAC
(VRRP is not a possibility for reasons not worth mentioning).
Two questions here:
- In some docs, I see mention of using SNAT on outgoing packets to keep
a connection hooked up with one router. That's only necessary for
multiple ISPs, right?
- Is this going to be more trouble than it's worth -- packet re-ordering
or some other unforeseen problems?
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2002-12-03 18:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 18:52 sabat [this message]
2002-12-04 4:14 ` [LARTC] Redundant Routes to *Same* ISP William L. Thomson Jr.
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=marc-lartc-103895650511474@msgid-missing \
--to=sabat@eloan.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 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.