Vito_Corleone wrote:
Steve, for this BGP manipulation, you're talking about being dual homed to a single provider, or dual homed to two providers? After talking to Noah (networker4034094394 on here), it seems like prepending is really the only option when you're dual homed to multiple providers. Again, my real world BGP experience is very limited, but I love learning about the protocol and how stuff works in the real world.
Dual (or more) homed to multiple providers. Providers perform the default actions I described before with transit, peers, and customers. If they didn't then allow you a mechanism to override that default behavior, you'd be fucked. You'd be able to influence *most* traffic with prepending but not all. And the bigger your provider is, the less traffic you'd have control over with prepending. This is something I designed for the ISP I worked at for 4 years and now use as a customer for 2 years at my current gig.
Take a look at this doc (
http://www.onesc.net/communities/as2828/):
Quote:
For our BGP customers, XO has implemented a powerful, flexible system whereby we allow our customers to control - via predefined communities - the XO treatment of their announcements. These communities control XO local-preference (local-pref) of customer-announced routes within our network.
The most powerful attribute is local-preference.
In BGP, the higher the local-pref, the more preferred the route on the network. This affects XO backbone route selection only, and not the route selection made by XO peers and customers, because localpreference is non-transitive. This means it does not get passed beyond the XO network. The customer has a range of six local-preferences to which they can set their routes.
What they won't put in writing is
why they treat customer routes this way and the answer is because it's the difference between revenue and an expense.
_________________
Find networking-forum.com on
Facebook,
LinkedIn,
Twitter,
Google+,or subscribe to the site's
RSS feeds.