Hi nagp, It’s not currently possible but it is achievable with a small amount of effort.
The encap side I think Is already possible. As you say, use l2-xcrw and xconnect the l2 sub-interface with an ‘mpls tunnel …’ interface. The MPLS tunnel will add the label stack of your choice and then route to the next-hop you define. However, the MPS tunnels are unidirectional, so the decap side is missing. To do decap we need a ‘mpls local-label …’ (a.k.a mpls route …), that maps the rx’d label to the mpls tunnel interface’s l2-input. I suggest a new ‘Interface DPO’ to represent this. There are other use cases for an interface-dpo too. Easily testable with ‘make test’ too ☺ If you want to take a shot at it, I will gladly assist. Regards, neale From: <vpp-dev-boun...@lists.fd.io> on behalf of Nagaprabhanjan Bellaru <nagp.li...@gmail.com> Date: Tuesday, 3 January 2017 at 11:25 To: vpp-dev <vpp-dev@lists.fd.io> Subject: [vpp-dev] L2 XConnect over MPLS? Hi, Is it possible to do L2 cross-connect over MPLS? For example: I want traffic coming in on a L2 sub interface to get punted on a MPLS tunnel (i.e. with MPLS encapsulation) and on the other side, pop the labels and switch the packet on the corresponding sub interface. Technically, a psuedowire across MPLS clould (VPWS) I see that we can use l2-xcrw to add a tunnel header and possibly some MPLS labels on the encap side, but I am not able to see how I can stitch things on the decap side - for example I cannot see how can I map an MPLS label to a L2 subinterface for the packet to go out.. Is it possible to do with VPP? Thanks, -nagp
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
