mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin Eriksson" <nitrax@giron.wox.org>
To: <linux-kernel@vger.kernel.org>
Cc: "Laurent Deniel" <deniel@worldnet.fr>
Subject: Re: Ethernet NIC dual homing
Date: Mon, 29 Oct 2001 14:24:24 +0100	[thread overview]
Message-ID: <001a01c1607d$06aca200$0201a8c0@HOMER> (raw)
In-Reply-To: <3BDC3F24.4D66FA0A@worldnet.fr>

----- Original Message -----
From: "Laurent Deniel" <deniel@worldnet.fr>
To: <linux-kernel@vger.kernel.org>
Sent: Sunday, October 28, 2001 6:23 PM
Subject: Ethernet NIC dual homing


>
> Hi,
>
> Does someone know if there is some work in the area of NIC dual homing ?
> By NIC dual homing, I mean two network devices (e.g. Ethernet) that are
> connected to the same IP subnet but only one is active (at IP level) at a
> time. When a faulty condition is detected (e.g. link down or lack of I/O),
> the kernel switches to the second NIC. Such a similar feature exists in
> Tru64 UNIX (NetRAIN), HP-UX (APA) and Solaris (Sun Cluster pnmd).
> What is the best way to handle that in Linux ? I thought about an IP
virtual
> device that could be mapped on two eternet NIC and some ioctl to switch
from
> one NIC to another or a generic virtual ethernet driver that could handle
two
> real ethernet drivers ?

Well, it shouldn't be too hard to modify the bonding driver to do something
like this (?), and instead the most work should (and will) go into the
user-space daemon. That way it would be possible not only to detect faulty
NIC hardware, but also to detect for example a faulty network segment.

Anyone wants to take a shot on this? I'm gonna look into it a bit, because
it sounds like a nice project for me as a linux-kernel-programmer newbie.

_____________________________________________________
|  Martin Eriksson <nitrax@giron.wox.org>
|  MSc CSE student, department of Computing Science
|  Umeå University, Sweden



  reply	other threads:[~2001-10-29 13:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-28 17:23 Laurent Deniel
2001-10-29 13:24 ` Martin Eriksson [this message]
     [not found] <Pine.LNX.4.10.10110281248320.5138-100000@coffee.psychology.mcmaster.ca>
2001-10-28 22:23 ` Laurent Deniel
     [not found] <Pine.LNX.4.10.10110281727070.5138-100000@coffee.psychology.mcmaster.ca>
2001-10-28 22:42 ` Laurent Deniel
2001-10-29 13:39 willy tarreau
2001-10-29 19:59 ` Laurent Deniel
2001-10-29 22:17   ` Laurent Deniel
2001-10-29 22:32     ` willy tarreau
2001-10-29 22:26   ` willy tarreau
2001-10-29 22:59     ` Christopher Friesen
2001-10-29 23:07       ` willy tarreau
2001-10-30  2:33       ` Dan Hollis
2001-10-30  2:55         ` Jonathan Lundell
2001-10-30  3:15           ` H. Peter Anvin
2001-10-30  3:30           ` Jonathan Lundell
2001-10-30  4:57             ` Dan Hollis
2001-10-30 15:33             ` Christopher Friesen
2001-10-30  4:55           ` Dan Hollis
2001-10-30 11:05 Chemolli Francesco (USI)
2001-10-30 11:33 ` Alan Cox
2001-10-30 11:14 Chemolli Francesco (USI)

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='001a01c1607d$06aca200$0201a8c0@HOMER' \
    --to=nitrax@giron.wox.org \
    --cc=deniel@worldnet.fr \
    --cc=linux-kernel@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

Powered by JetHome