Date: Fri, 27 Oct 2006 10:10:19 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: "Mark Sellers" <mark.sellers@hamiltontel.com> Cc: freebsd-questions@FreeBSD.org Subject: Re: dual homing a freebsd server Message-ID: <44u01prgs4.fsf@be-well.ilk.org> In-Reply-To: <auto-000044970744@hamilton.net> (Mark Sellers's message of "Wed, 25 Oct 2006 13:21:52 -0500") References: <auto-000044970744@hamilton.net>
next in thread | previous in thread | raw e-mail | index | archive | help
"Mark Sellers" <mark.sellers@hamiltontel.com> writes: > I want to put two nic cards in a server, and have two separate gateways > assigned to each nic. I want one to master and the other slave. When the > primary network dies I want it to failover to the other card on the fly. > > > > Any help would be greatly appreciated. Technically, that isn't multi-homing, because you aren't planning to use both links at the same time. You might have gotten more responses if you had referred to "failover" in your subject line. There are a number of ways to do what you're looking for, but they will break existing connections when the failover occurs. That may or may not be a problem, depending on how long-lived the critical connections are for your server (and whether it can re-establish them on its own when they fail). There are some programs in ports that claim to do this sort of thing (e.g., net/balance), but I haven't used any. In general, the difficult part is detecting the failure -- if that problem is solved, scripting the failover is trivial. Note that the failure will typically not be on your physical link, so you can just watch the local interface. In the worst case, you use some kind of heartbeat protocol with a carefully-chosen router on your primary network, but there may be a better way depending on the precise configuration of that network. Good luck. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44u01prgs4.fsf>