[j-nsp] IPv6

[Mark Tinka]

On Sunday 24 January 2010 01:31:22 am Richard A Steenbergen 
wrote:

> * Juniper does something weird with next-hop self, which
>  causes a lot of grief when you want to do ipv4/ipv6 dual
>  stack. Basically the problems is there isn't an
>  "update-source <interface>" option like Cisco has, so
>  the next-hop self value is taken from the local address
>  of the BGP session rather than from any particular
>  interface. So when you carry ipv4+piv6 AFIs over a
>  single IBGP session (using for example an IPv4 address
>  as transport), and you do a next-hop self, it sets the
>  v6 nexthop to ::i.p.v.4 rather than a proper v6 address.
>  You can avoid setting next-hop self in most cases, but
>  it's pretty hard to avoid when you're doing prefix
>  origination. IMHO the easiest way to work around this is
>  just to make an ::i.p.v.4 alias on your lo0 and carry
>  both values in your IGP, but it's something to keep in
>  mind.

Curious, did you have any particular reasons you chose to 
carry both v4 and v6 NLRI in a single iBGP session, as 
opposed to running independent sessions for each AFI on the 
same wire?

Cheers,

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