From owner-freebsd-questions@FreeBSD.ORG Tue Jul 30 07:42:57 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 46904409; Tue, 30 Jul 2013 07:42:57 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail05.adl6.internode.on.net (ipmail05.adl6.internode.on.net [IPv6:2001:44b8:8060:ff02:300:1:6:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9CB95296F; Tue, 30 Jul 2013 07:42:56 +0000 (UTC) Received: from ppp247-71.static.internode.on.net (HELO leader.local) ([203.122.247.71]) by ipmail05.adl6.internode.on.net with ESMTP; 30 Jul 2013 17:12:54 +0930 Message-ID: <51F76E7A.40504@ShaneWare.Biz> Date: Tue, 30 Jul 2013 17:12:50 +0930 From: Shane Ambler User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130516 Thunderbird/17.0.6 MIME-Version: 1.0 To: "Zyumbilev, Peter" Subject: Re: 2 lines References: <51F66820.4080907@aboutsupport.com> <51F668E2.4090806@aboutsupport.com> <1375105599.9477.2811311.2C84EDDD@webmail.messagingengine.com> <51F69A9F.3050800@aboutsupport.com> <51F6A128.6060903@FreeBSD.org> <51F7505B.3090200@aboutsupport.com> In-Reply-To: <51F7505B.3090200@aboutsupport.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Matthew Seaman , freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jul 2013 07:42:57 -0000 On 30/07/2013 15:04, Zyumbilev, Peter wrote: > However really not sure what is the best way - the only feasible > solution I found so far is DNS faiolver > http://www.dnsmadeeasy.com/services/dns-failover-system-monitoring/. > However I am not 100% sure how well it will work and if this may cause > more troubles and embarrassment in front of the customer than simply > giving them in a email > > gate1.example.com(primary) > gate2.example.com(backup) I thought pfsense supported failover - or is that limited to outgoing? http://doc.pfsense.org/index.php/File:RouterDiagram.png http://www.techvilleottawa.org/pfsense-load-balance-fail-over-setup/ Otherwise something like wackamole or heartbeat to keep the ip address alive?