redundant NICs

Hans Fugal hans at
Fri Jul 22 01:11:24 MDT 2005

On Thu, 21 Jul 2005 at 22:01 -0600, Lars Rasmussen wrote:
> On 7/21/05, Hans Fugal <hans at> wrote:
> > 1 Server, 1 IP, 2 NICs.  Load balancing would be nice, redundancy is the
> > primary goal. i.e. if a NIC dies, life goes on over the alternate NIC
> > without interruption.
> > 
> > Google points me towards bonding the NICs
> > (Documentation/networking/bonding.txt) but I wondered if anyone had done
> > this and what approach you took.
> Hans,
> I don't know how to do this with one server and 2 NICs.  I'd be more
> worried about fan, power supply, or hard drive failure(all moving
> parts)than NIC failure.  

All redundant already, and I've seen two NICs fail in important boxes in
the past year, tying for first place with power supplies.

> With 2 servers you can setup CARP with a
> virtual IP as the internal gateway for high availability.  If one of
> the interfaces dies or one server goes down, the other takes over, and
> the gateway IP is always the same.   pfSense (
> will do this - get version 70.8 or later.  It's based on FreeBSD 6 -
> and can boot off a LiveCD initially.  You can opt to install to a hard
> drive, CF card with IDE bridge, or use Soekris/PC Engines Wrap (no
> moving parts) boards.
> Did I mention you get traffic shaping(QoS) as well?
> Check #pfsense on freenode IRC to ask the developers questions.

Sounds interesting, but it looks like bonding will do the trick.


 .O.  Hans Fugal            | De gustibus non disputandum est.
 ..O | Debian, vim, mutt, ruby, text, gpg
 OOO                        | WindowMaker, gaim, UTF-8, RISC, JS Bach
GnuPG Fingerprint: 6940 87C5 6610 567F 1E95  CB5E FC98 E8CD E0AA D460
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : 

More information about the PLUG mailing list