From: Jose Luis Domingo Lopez <lartc@24x7linux.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Configuring a redundant ethernet connection
Date: Wed, 22 Jan 2003 20:22:58 +0000 [thread overview]
Message-ID: <marc-lartc-104326708232465@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104324662830977@msgid-missing>
On Wednesday, 22 January 2003, at 10:07:32 -0600,
Martin A. Brown wrote:
> : 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.
>
> Linux supports channel bonding which should do what you want. There is
> little documentation outside the kernel for this, but what documentation
> exists is very good. This can be found in a linux source tree in the
> following file:
>
As far as I know ethernet bonding (trunking) is a layer-2 point-to-point
thing. So you need compatible bonding implementations at both sides, and
every cable in the trunk on each end must go to the same box.
The original poster said "dual ethernet connections to the same IP
subnet (but different switches)", so I'm afraid bonding is not an option.
Regards,
--
Jose Luis Domingo Lopez
Linux Registered User #189436 Debian Linux Sid (Linux 2.4.20-xfs)
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-01-22 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 14:42 [LARTC] Configuring a redundant ethernet connection Doug Kingston
2003-01-22 16:07 ` Martin A. Brown
2003-01-22 20:22 ` Jose Luis Domingo Lopez [this message]
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-104326708232465@msgid-missing \
--to=lartc@24x7linux.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.