""Jim Devane"" wrote in message news:[EMAIL PROTECTED] > hello all, > > (Re-post...not sure if original msg made it our not) > > playing around again and have a question. eBGP multi-hop cannot come up if > the peer is known through a default route. > Is there a reason why? > I mean, what is the point of a static route that causes a recursive lookup > or a static route that simply points to the same next hop as a default route? > For that matter, I can't see it being a matter of proximity either. If > convergence time were not an issue, what is really wrong with having a 10 > hop or even 50 hop BGP session? (I know it is unlikely and there are > cetainly better ways to handle it (GRE or IPSec tunnel)) but for the sake of > argument...
I've done BGP peering with other folks across the internet - as many as 25 hops away. It's doable with no problems, so long as your provider is not filtering BGP somewhere. > > Just curious, not able to find much on WHY it is like this... > I've run into this problem as well. My theory - it's part of the code, requiring a specific route to a peer. BGP in general is not supposed to do much of anything with any information unless there is a specific route in the router's routing table. Counter intuitive, but rational in that BGP is meant to be reliable, and dependence on a default route is not reliable. > thanks, > Jim Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=65850&t=65823 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
