From owner-freebsd-security Tue Apr 6 20:57:17 1999 Delivered-To: freebsd-security@freebsd.org Received: from trooper.velocet.ca (trooper.velocet.net [209.167.225.226]) by hub.freebsd.org (Postfix) with ESMTP id 25D1315041 for ; Tue, 6 Apr 1999 20:57:15 -0700 (PDT) (envelope-from dgilbert@trooper.velocet.ca) Received: (from dgilbert@localhost) by trooper.velocet.ca (8.8.7/8.8.7) id XAA11017; Tue, 6 Apr 1999 23:55:04 -0400 (EDT) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14090.55064.212139.89533@trooper.velocet.ca> Date: Tue, 6 Apr 1999 23:55:04 -0400 (EDT) To: "GuangChun Wen" Cc: Subject: Cluster service in FreeBSD In-Reply-To: <00b201be809b$ced53cc0$b366b4cb@wen.iisi.co.jp> References: <00b201be809b$ced53cc0$b366b4cb@wen.iisi.co.jp> X-Mailer: VM 6.62 under Emacs 19.34.2 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> "GuangChun" == GuangChun Wen writes: GuangChun> Hi everyone: I am planning to use Freebsd as our firewall. GuangChun> I wonder if there are ports or products which can GuangChun> automatically balancing the loads between several servers, GuangChun> or takes over failed server with another server,maybe like GuangChun> cluster service in NT? GuangChun> I wonder if anybody can give me information about documents GuangChun> which describe such techniques. While I'm sure that they do it differently with NT, I'd guess that you could effectively do this with some fancy routing protocols with BSD. But... then there's the issue that with NT... you want to plan for failure 'cause it's so common. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message