Hi Jim, I'm not sure how your peering is configured, but BGP uses TCP to establish sessions and the default TTL of these packets is set to 1. If your peer is more than 1 hop away, the BGP packet will never reach its intended peer.
HTH, Elmer -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, March 20, 2003 7:35 AM To: [EMAIL PROTECTED] Subject: eBGP Multi-hop [7:65823] 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... Just curious, not able to find much on WHY it is like this... thanks, Jim Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=65836&t=65823 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
