From owner-freebsd-hackers Sat Apr 25 15:14:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28938 for freebsd-hackers-outgoing; Sat, 25 Apr 1998 15:14:43 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.artcom.de ([192.76.129.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28874 for ; Sat, 25 Apr 1998 15:14:35 -0700 (PDT) (envelope-from hans@artcom.de) Received: from transrapid.artcom.de by mail.artcom.de with smtp id m0yTDCr-00000nC; Sun, 26 Apr 1998 00:14:01 +0200 (MEST) Date: Sun, 26 Apr 1998 00:14:01 +0200 (MEST) From: Hans Huebner To: Mattias Pantzare cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD HA configuration / Ethernet address takeover In-Reply-To: <199804252115.XAA14964@zed.ludd.luth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Why do it at the eternet level and not at the IP level? Doing it at the IP > level will give the same functionality if the only protocol that you are > using is IP. All the support is already there. Just set up two IP adresses > on the server that is covering for the failing server, the normal IP and the > IP of the failing server. Because that requires re-arping of the IP address in the failover case. Also, I'm not sure whether I want to restrict the HA configuration to IP only. Supporting AppleTalk failover would also be useful. > If you do it at the ethernet level then the backup server can't be used for > other things as its's ethernet adress will disapear if you change the ethernet > adress on it. For a good HA configuration, multiple ethernet interfaces are useful anyway. Also, many ethernet chips support multiple ethernet addresses on a single ethernet interface. Hans To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message