From: Doug Kingston <douglas.kingston@db.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Configuring a redundant ethernet connection
Date: Wed, 22 Jan 2003 14:42:56 +0000 [thread overview]
Message-ID: <marc-lartc-104324662830977@msgid-missing> (raw)
I am interested in setting up a host with dual ethernet connections to the same
IP subnet (but different switches) for redundancy. We need reasonably
transparent failover if an interface fails. In studying the existing HOWTO
documents and other stuff produced by Google, it looks like the configuration in
section 4.2 of the HOWTO (Routing for multiple uplinks/providers) comes close to
setting up what we need, but there are some issues:
1. As implemented, traffic is segrated by destination and transparent failover
is not possible. If an interface fails, connections would need to be
re-established.
2. Traffic is sourced with an interface specific address.
3. Incoming traffic would be bound to one or the other and at best would need to
rely on something like DNS round robin at connection setup time - not ideal.
Though I have not tried this yet, it looks like one might be able to setup a
dummy interface with a third IP address on the same subnet, and then proxy arp
for that address from either of the real interfaces. This virtual address is
the one you would advertise via DNS as the machine's "primary" address, and this
address would be used as the Source address on all outgoing packets.
Has anyone attempted to set up a redundant interface in this manner or something
similar? How would I arrange for the proxy arping that would be necessary to
get traffic for the virtual interface delivered to the real one? Is there a
better way?
If I get this working - I will write up the HOWTO...
-Doug-
--
Douglas Kingston
Director
Global Unix Engineering Manager
Deutsche Bank AG London
6 Bishopsgate
London EC2N 4DA
Work: +44-20-7545-3907
Mobile: +44-7767-616-028
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-01-22 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 14:42 Doug Kingston [this message]
2003-01-22 16:07 ` [LARTC] Configuring a redundant ethernet connection Martin A. Brown
2003-01-22 20:22 ` Jose Luis Domingo Lopez
2003-01-23 9:13 ` Doug Kingston
2003-01-24 1:31 ` Jose Luis Domingo Lopez
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-104324662830977@msgid-missing \
--to=douglas.kingston@db.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.