:[EMAIL PROTECTED] On
Behalf Of
Jim Devane
Sent: Thursday, March 20, 2003 9:28 AM
To: [EMAIL PROTECTED]
Subject: Re: eBGP Multi-hop [7:65823]
Thanks for the replies so far...
Hmm, Well, actually becuase BGP uses TCP 179 is can traverse
non-BGP
speakers to a router that does speak BGP
Dial/Security)
[EMAIL PROTECTED]
http://www.labforge.com
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of
Jim Devane
Sent: Thursday, March 20, 2003 9:28 AM
To: [EMAIL PROTECTED]
Subject: Re: eBGP Multi-hop [7:65823]
Thanks
]
Subject: RE: eBGP Multi-hop [7:65823]
A default route, aka a route of last resort. For BGP, route to the next
hope must be explicitly in the routing table. This is one of the
pre-reqs
for BGP to advertise its own routes as well (unless you have
synchronisation
turned off).
In my deployments of BPG
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
] [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
I guess I am kind of just going to a quick stab. Do you have no
synchronization under the BGP configuration?
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
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
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
I'll guess and say this is an accident prevention mechanism. Suppose
you have two egress points and each advertises a default. If the link
from one of these egress devices to its peer fails, might the eBGP
session
remain up, but follow the default through the other egress location?
You wouldn't
-reconfiguration inbound
neighbor 172.16.10.1 password 7 140705191C117B3821
neighbor 172.16.10.1 filter-list 3 in
neighbor 172.16.10.1 filter-list 4 out
- Original Message -
From: Carroll Kong
To:
Sent: Thursday, March 20, 2003 6:54 AM
Subject: Re: eBGP Multi-hop [7:65823]
I guess I am
Ah!
ok, I guess I can make do with that.
They just want you to be deliberate about the config.
Ok, cool,
THANKS!
jim
- Original Message -
From: John Neiberger
To:
Sent: Thursday, March 20, 2003 8:10 AM
Subject: Re: eBGP Multi-hop [7:65823]
hello all,
(Re-post...not sure
Thanks for the replies so far...
Hmm, Well, actually becuase BGP uses TCP 179 is can traverse non-BGP
speakers to a router that does speak BGP ( Just like TFTP'ing to another
router)
I put the config I was testing below. The config works, BGP runs everyone is
happy when I have a specific route to
:[EMAIL PROTECTED] On Behalf Of
Jim Devane
Sent: Thursday, March 20, 2003 9:28 AM
To: [EMAIL PROTECTED]
Subject: Re: eBGP Multi-hop [7:65823]
Thanks for the replies so far...
Hmm, Well, actually becuase BGP uses TCP 179 is can traverse non-BGP
speakers to a router that does speak BGP ( Just like
13 matches
Mail list logo
