[j-nsp] LSP's with IPV6 on Juniper

[Olivier Benghozi]

In global we have 6PE.
In VRF we have 6VPE.
Just works so far.

An yes, the MPLS control-plane uses only IPv4: (the intercos between routers are in IPv4, LDP uses IPv4, IGP uses IPv4, and IPv6 is really announced over specific AFI/SAFI (labeled unicast IPv6 for 6PE, VPNv6 for 6VPE) in IPv4 MP-iBGP sessions ; but it doesn't matter.

Of course the actual IPv6 loopbacks won't go to inet6.3 since they are not used to resolve the routes (you will see your IPv4 mapped over IPv6 addressing). The next-hops are IPv4, but again, it doesn't matter, only the results matter: it works :)

You don't explicitly "change" the next-hop of IPv6 using policies, you just use nexthopself and that's it.

> Le 27 août 2018 à 18:39, craig washington <craigwashington01 at hotmail.com> a écrit :
> 
> Hello all.
> 
> Wondering if anyone is using MPLS with IPV6?
> 
> I have read on 6PE and the vpn counterpart but these all seem to take into account that the CORE isn't running IPV6?
> 
> My question is how can we get the ACTUAL IPV6 loopback addresses into inet6.3 table? Would I need to do a rib import for directly connected?
> 
> If you run "ipv6-tunneling" this seems to only work if the next-hop is an IPV4 address. (next-hop self)
> 
> I also messed around with changing the next-hop on the v6 export policy to the IPV4 loopback and this works too but figured there should be a different way?
> 
> So overall, I am trying to find a way for v6 routes to use the same LSP's as v4 without changing the next hop to a v4 address.
> 
> Hope this makes sense 😊
> 
> 
> Any feedback is much appreciated.
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp