From owner-freebsd-questions@FreeBSD.ORG Tue Nov 4 16:12:16 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98F8F16A4CE for ; Tue, 4 Nov 2003 16:12:16 -0800 (PST) Received: from be-well.no-ip.com (lowellg.ne.client2.attbi.com [66.30.200.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id D288E43FA3 for ; Tue, 4 Nov 2003 16:12:15 -0800 (PST) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: by be-well.no-ip.com (Postfix, from userid 1147) id 17EEE3B09; Tue, 4 Nov 2003 19:12:15 -0500 (EST) Sender: lowell@be-well.ilk.org To: "Bryce Edwards" References: <015901c3a244$1b090e40$67320a0a@gis2.com> From: Lowell Gilbert Date: 04 Nov 2003 19:12:14 -0500 In-Reply-To: <015901c3a244$1b090e40$67320a0a@gis2.com> Message-ID: <44n0bb3c81.fsf@be-well.ilk.org> Lines: 19 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-questions@freebsd.org Subject: Re: Dual Interface Server Setup X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Nov 2003 00:12:16 -0000 "Bryce Edwards" writes: > I need help with a server configuration. I need to setup some FreeBSD > servers that have dual interfaces. I would like the servers to have one IP > address, and I would like them to use both interfaces in a fault tolerant > setup, so that a link or switch failure to either one can be sustained. The > interfaces are connected to separate switches and I would like them to be a > member of the same VLAN and not have STP enabled if at all possible. TIA! That's an awful lot of work you're going to. If you really want to shoot your foot off, it's not necessary to take such careful aim. Most of what you're trying isn't really that hard; you want to configure one of the interfaces, and keep the other "down" until the first develops a problem, then bring the first one down and raise the second with the same IP configuration. The hard part is *detecting* any problems, especially without running a spanning tree. You'll need to do some sort of hack, probably at the IP layer, to raise an alarm when connectivity to some specific destination fails.