From owner-freebsd-isp@FreeBSD.ORG Tue Sep 2 07:46:36 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 EAF9316A4C0 for ; Tue, 2 Sep 2003 07:46:36 -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 815DC43F85 for ; Tue, 2 Sep 2003 07:46:35 -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 A0A4B2F993; Tue, 2 Sep 2003 10:46:49 -0400 (EDT) Date: Tue, 2 Sep 2003 10:46:49 -0400 From: Haesu To: Tom , freebsd-isp@freebsd.org Message-ID: <20030902144649.GA34440@scylla.towardex.com> References: <0AF1BBDF1218F14E9B4CCE414744E70F07DF30@exchange.wanglobal.net> <20030901191048.GA93348@scylla.towardex.com> <20030901211636.Y58733@light.sdf.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030901211636.Y58733@light.sdf.com> 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: Tue, 02 Sep 2003 14:46:37 -0000 > > Plus, some have suggested just advertising your existing assignments > from your other provider. Bad idea. Most providers address allocated > is not portable. Check WHOIS for "ADDRESSES WITHIN THIS BLOCK ARE > NON-PORTABLE". Besides, even if your existing provider's IP blocks work, > and your provider allows you to do this (you should always ask first), > you'll be advertising a more specific prefix of one of their larger > blocks. Guess what that will do? Obviously you have not had enough experience working with BGP customers. Longer matches always win. Your provider announces the aggregate. It's funny to say I've had up to /20 being announced elsewhere with provider's permission even when whois shows ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE. Most providers will not care as long as you can justify why you want to announce the block elsewhere, and as long as you properly register them at IRR. Yes IRR routing registry is only as good as the networks that use it. But you know what? Major carriers do use them, and those who filter routes on RIR registration boundaries either a) point a default route to elsewhere or b) build filter based on IRR. Try peering with some big national carrier-- they will not peer with you if you do not use IRR -- especially in US. Frankly, if you are a backbone filtering /24s, you obviously don't know where to get to the internet if you are not even using IRR. Even our good old friends at Verio is accepting our announced /24's now as long as registered in the IRR. > But you need to know what you doing. If you dump the routing table, > you'll see that many networks can't even do basic route summaries. You mean aggregation? I don't follow. -hc -- Sincerely, Haesu C. TowardEX Technologies, Inc. WWW: http://www.towardex.com E-mail: haesu@towardex.com Cell: (978) 394-2867 > > > -hc > > > > -- > > Sincerely, > > Haesu C. > > TowardEX Technologies, Inc. > > WWW: http://www.towardex.com > > E-mail: haesu@towardex.com > > Cell: (978) 394-2867 > > > Tom > _______________________________________________ > 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"