>Tnx a lot Scott.
>
>I'm still not there. The more I think about it, the more I get confused. I
>only have more questions.
>You remark about the AS# cleared up some things though. Obviously the
>AS-path attribute is the only means by which BGP is able to tell where a
>routing update contains a loo
Tnx a lot Scott.
I'm still not there. The more I think about it, the more I get confused. I
only have more questions.
You remark about the AS# cleared up some things though. Obviously the
AS-path attribute is the only means by which BGP is able to tell where a
routing update contains a loop, that
First of all, BGP has no "split horizon" rule. IBGP neighbors will not
propagate routes to each other as a matter of loop protection (since we have
no way to add AS numbers w/in the AS--don't worry about confederations yet).
This really has nothing to do w/split horizon. Try this:
R1R2---R3
The BGP split horizon rule is confusing me.
It states that routes learned by a IBGP router are not propagated to other
IBGP routers.
I guess this only regards IGP learned routes and trying to avoid that an
IBGP router learns a IGP route before other parts of the AS which are needed
for this route
4 matches
Mail list logo
