anycasting behind different ASNs?

Deepak Jain deepak at
Wed Dec 6 22:23:03 UTC 2006

> An easy way around this is to be consistent about your transit and 
> peering arrangements across locations.  If your anycast network has 
> transit from a network in one location, get transit from them in your 
> other locations, and let hot potato routing do its thing.  For cases 
> where this isn't practical, or where you want more control over who is 
> sending traffic to a node, declare the node to be a "peering only" node 
> and make sure your peers aren't leaking the anycast routes to their out 
> of region upstreams.

Or prepend (gasp!) like the Dickens for your "peering only" node to have 
transit, but be the route chosen after transit/connectivity to your 
"transit/peering ok" node fails.


More information about the NANOG mailing list