North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Easy and hard multihoming (was: Re: Upstreams blocking /24s)

  • From: David Barak
  • Date: Wed Oct 10 14:46:04 2007
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024;; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=N/ep9oa5iOYXoCCytlzNRgsm/rF01DJxopHOFmgovbcGrLOPUOFZqmnHJcnnCMNgx6DHckLUewuZFwVPZvHZhG3wMFgpu4MY2r30QhUe4xFcAqS79RNQBkrhAPoNaGFOT0kEOZSrn4Bsi+9K5+li62fhNEgOjAK0ycahM/AWRmU=;

--- [email protected] wrote:

> So if one of 
> the Tier I's decides not to accept my public /29
> then the millions of 
> singlehomed subscribers go with it.  

Yep.  During normal operation, someone would be
announcing the aggregate out of which your /29 is
carved, and that provider should be someone you're
paying to carry the more-specific.  Traffic will get
to you in that case.  If your circuit to that provider
goes down, then the other customers of your other
provider will be able to reach you, but the peers and
suppliers of your other provider would likely not.

The easiest way to multihome in a way which mostly
works (tm) is to get an ASN and self-originate a
prefix which is /24 or larger.  As of right now,
multihoming is a justification for a /24 and an ASN,
so multihoming in a different way should be something
which is done for a specific reason, or to solve a
particular problem.

Yes, yes, there are multiple other ways to do this,
but their failure modes might not be as easy for your
providers to help you troubleshoot as BGP is.


David Barak
Need Geek Rock?  Try The Franchise:

Need a vacation? Get great deals
to amazing places on Yahoo! Travel.