From owner-freebsd-isp@FreeBSD.ORG Mon Sep 1 12:10:35 2003 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31A7816A4BF for ; Mon, 1 Sep 2003 12:10:35 -0700 (PDT) Received: from mx01.bos.ma.towardex.com (a65-124-16-8.svc.towardex.com [65.124.16.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2753D44003 for ; Mon, 1 Sep 2003 12:10:33 -0700 (PDT) (envelope-from haesu@mx01.bos.ma.towardex.com) Received: by mx01.bos.ma.towardex.com (TowardEX ESMTP 3.0p11_DAKN, from userid 1001) id 7E7462F921; Mon, 1 Sep 2003 15:10:48 -0400 (EDT) Date: Mon, 1 Sep 2003 15:10:48 -0400 From: Haesu To: Sten Daniel S?rsdal , freebsd-isp@freebsd.org Message-ID: <20030901191048.GA93348@scylla.towardex.com> References: <0AF1BBDF1218F14E9B4CCE414744E70F07DF30@exchange.wanglobal.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0AF1BBDF1218F14E9B4CCE414744E70F07DF30@exchange.wanglobal.net> User-Agent: Mutt/1.4.1i Subject: Re: Multi-Homed Routing X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Sep 2003 19:10:35 -0000 On Mon, Sep 01, 2003 at 11:24:33AM +0200, Sten Daniel S?rsdal wrote: > [.snip.] > > > > this solution would work if you had alot of extra cash > > stashed away, just > > waiting to be used, which i dont think is the case here. yes > > bgp is the > > accepted solution but is way too expensive to implement. > > > Aye Yes and no. If you use some residential ISP or some cheapo local isp that doesnt even know how to configure BGP, then yes it is expensive path to take. If you already have competant provider as your upstreams, turning up bgp is just a matter of typing 'portinstall zebra' and get AS number from RIR and request minimum of /24 from LIR. Then just register your /24 at ALTDB for free. BGP *may* be expensive, but it truly is scalable and fully configurable for hosting applications. I.e. I can play the whole BGP game to route x amount of my customers via some cheap bandwidth provider, or some cust blocks out via premium bandwidht providers, etc, etc It's definately a powerful tool if you are up for it. -hc -- Sincerely, Haesu C. TowardEX Technologies, Inc. WWW: http://www.towardex.com E-mail: haesu@towardex.com Cell: (978) 394-2867 > > > > > > However. > > > > > > You could achieve almost the same effect by using a script to > > > check if both gateways are up and if one goes down it automatically > > > changes the default route to the working ISP. > > > Then automatically adjust your DNS pointers to the new ip > > address(es). > > > > kudos to the venerable ping. > > Kudos! > > > > > > > > > Your public ip address(es) will change, and hence some people wont > > > be able to reach your site until their DNS's are updated. Some > > > people have caching DNS's that wont expire a record for a long time > > > to not generate alot of traffic and wont reach your site at all. > > > > > > > Stan, Cant someone use dyndns? wouldnt it be easier to use? > > Sten :) > > Dyndns is one of many similar solutions, of course someone could use dyndns. > I do believe that dyndns has the same "flaw" i describe above, but that is a > local dns management issue. So yes. > > _______________________________________________ > freebsd-isp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-isp > To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"