[j-nsp] Redistribute Connected

[Mark Tinka]

On Tuesday 25 November 2008 13:53:38 Frans Legdeur wrote:

> Also ensure that unknown segments
> are advertised internally, so including the /30 between
> you and your transit neighbor, else your other router
> doesn't know where he can find his next hop for the i-BGP
> routes. (There are other ways to solve this, like
> next-hop self or add the interface passive to OSPF/ISIS,
> but this is the best way to my opinion ;-)

I think setting the NEXT_HOP attribute within iBGP, by 
default, is a best practice. I'd caution against any other 
method.

I personally don't prefer to carry foreign addresses within 
my IGP, but this topic has already been hashed out on this 
list in great detail...

Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20081125/bb78c385/attachment.bin>