<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.5730.11" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>>My guess is that if you had two NICs on the same
subnet with<BR>>different IPs the kernel route table and ARP cache would get
pretty<BR>>confused. This seems so incredibly broken to me I've never
tried....<BR>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>That was my guess and point to begin with. I
was not aware of or thinking about bonding. Without something out of the
ordinary in the protocol stack, there is no way to determine which NIC the OS
will use for a given destination IP, since either can get there. That is
why the hi-rel stuff I do has two parallel LANS with different subnets. It
places more of the burden on the program to know how to do backup, but I control
the code in the projects I'm doing, so its not a problem.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Wilton</FONT></DIV></BODY></HTML>