From owner-freebsd-net Fri May 4 22:18:14 2001 Delivered-To: freebsd-net@freebsd.org Received: from Spaz.HuntsvilleAL.COM (spaz.huntsvilleal.com [63.147.8.31]) by hub.freebsd.org (Postfix) with ESMTP id 7507637B424; Fri, 4 May 2001 22:18:06 -0700 (PDT) (envelope-from kris@catonic.net) Received: from localhost (kris@localhost) by Spaz.HuntsvilleAL.COM (8.11.3/8.11.3) with ESMTP id f455HeQ24107; Sat, 5 May 2001 05:17:40 GMT Date: Sat, 5 May 2001 05:17:40 +0000 (GMT) From: Kris Kirby X-Sender: kris@spaz.huntsvilleal.com To: Ted Mittelstaedt Cc: Wai Chan , freebsd-net@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: RE: outgoing traffic load balancing with multiple ISP In-Reply-To: <000001c0d455$00a50fa0$1401a8c0@tedm.placo.com> Message-ID: X-Tech-Support-Email: bofh@catonic.net MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 3 May 2001, Ted Mittelstaedt wrote: > This gains ISP#1 multiple paths to ISP#2 - ie: More > Bandwidth. Plus, it gives them a redundant backup in case their > direct link to ISP#2 goes down. > > In exchange for this ISP#1 agrees to credit your bill to > zero - in effect, you are now serving as a feed to them > that costs them nothing. I'm going to veto that one. I've read (alas, I'm not yet a BGP admin) that you can prepend your own AS as a method of equilization. As this scenario unfolds, you have two pipes which eventually diverge. You prepend your AS to the ISP #1 route (the big upstream) so that it's advertised as two hops, and then route normally for the other ISP (the five-year contract one). The net result should be two equal-cost routes back to your NOC even though it goes to two ISPs (really one). Make sense? ----- Kris Kirby, KE4AHR | TGIFreeBSD... 'Nuff said. | ------------------------------------------------------- "Fate, it seems, is not without a sense of irony." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message