Hi
For the MPLS L3VPN the answer is that the next hop attribute needs to be
an address from the default VRF and if the peering is happening in a VRF
context, there is no address from the default VRF you could use as next
hop other than self.
This can be rather inconvenient as there are advan
I'd like to add that one major advantage is limiting next-hops, thus
labels in your network. This is not just theoretical concern but there
are plenty of practical networks using practical hardware where you
simply cannot expose all next-hops to every node.
On 1 December 2017 at 17:30, Ken Chase
On an IX, without next-hop-self peer A leaking peer B's routes they receive to
C will have C send direct to B on the IX (assuming flat layer 3 addressing,
and not multiple little /30s or /96s everywhere or something - do any
exchanges do that?)
This may seem more efficient than sending C's traffic
3 matches
Mail list logo
