Skip to contentSkip to conversation

Ethernet NIC dual homing

DISCUSSION Laurent Deniel 2 participants 2 messages Oct 28, 2001 – Oct 29, 2001

lore
Share & tools
lore
#0 lore raw

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 ?

Laurent

PS: please CC to me since I do not read lkml at a regular basis. TIA.

#1 lore raw

----- Original Message -----
From: "Laurent Deniel" <[email protected]>
To: <[email protected]>
Sent: Sunday, October 28, 2001 6:23 PM
Subject: Ethernet NIC dual homing

Quoted 10 lines

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

Quoted 1 line

device that could be mapped on two eternet NIC and some ioctl to switch

from

Quoted 1 line

one NIC to another or a generic virtual ethernet driver that could handle

two

Quoted 1 line

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 <[email protected]>
|  MSc CSE student, department of Computing Science
|  Umeå University, Sweden