From owner-freebsd-questions@FreeBSD.ORG  Mon Jul 29 13:46:41 2013
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
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 4BD9B452
 for <freebsd-questions@freebsd.org>; Mon, 29 Jul 2013 13:46:41 +0000 (UTC)
 (envelope-from feld@FreeBSD.org)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com
 [66.111.4.25])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 20BD3273D
 for <freebsd-questions@freebsd.org>; Mon, 29 Jul 2013 13:46:41 +0000 (UTC)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42])
 by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id C367220960
 for <freebsd-questions@freebsd.org>; Mon, 29 Jul 2013 09:46:39 -0400 (EDT)
Received: from web3 ([10.202.2.213])
 by compute2.internal (MEProxy); Mon, 29 Jul 2013 09:46:39 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
 messagingengine.com; h=message-id:from:to:mime-version
 :content-transfer-encoding:content-type:subject:date:in-reply-to
 :references; s=smtpout; bh=wGMTdunx2Rtd7mNSuf8ARRlTlWs=; b=fOWbZ
 Nw55YAnIqeIsMPLs1qhhsv6Y7DdYP2lw6xuiAXPzH+bp0ZFGyLDms+WSpa4Jitun
 7eSUBIuKBfQrI3MosSG+SgXL8klR/7tz4fTjZLnUj4DFMPpUnHueBaNQ/PG+jMyQ
 TJLsk6/lF91pTuqnB5HnS1BI4RoQR5mb27V4Vg=
Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99)
 id A916EB01E70; Mon, 29 Jul 2013 09:46:39 -0400 (EDT)
Message-Id: <1375105599.9477.2811311.2C84EDDD@webmail.messagingengine.com>
X-Sasl-Enc: is3nqJnvzh7thP/TY3tcTuxjc02P6Y2kMq3onPkHdhrN 1375105599
From: Mark Felder <feld@FreeBSD.org>
To: freebsd-questions@freebsd.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-23e62cd3
Subject: Re: 2 lines
Date: Mon, 29 Jul 2013 08:46:39 -0500
In-Reply-To: <51F668E2.4090806@aboutsupport.com>
References: <51F66820.4080907@aboutsupport.com>
 <51F668E2.4090806@aboutsupport.com>
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jul 2013 13:46:41 -0000

The right way to handle this is to get your own IP allocation and do BGP
out both providers. Then the internet can reach you over both internet
connections and when one goes down all traffic is routed through your
other connection.

Another feasible, but poor option: proxy your services out in the cloud
and have it be intelligent enough to be able to reach your content over
both providers and properly failover when one goes down.