[ovs-dev] Error after inserting MPLS flow using OVS2.0

[Ben Pfaff]

On Fri, Feb 07, 2014 at 06:09:45PM -0800, Madhusudhan Kandadai wrote:
> But, when I try to attempt in pushing two mpls header for a flow, I
> could not see two labels while using tcpdump that means, the packets
> are not flowing through it. So, I had an idea to make it work.

Did you read the FAQ?

Q: Does Open vSwitch support MPLS?

A: Before version 1.11, Open vSwitch did not support MPLS.  That is,
   these versions can match on MPLS Ethernet types, but they cannot
   match, push, or pop MPLS labels, nor can they look past MPLS labels
   into the encapsulated packet.

   Open vSwitch versions 1.11, 2.0, and 2.1 have very minimal support
   for MPLS.  With the userspace datapath only, these versions can
   match, push, or pop a single MPLS label, but they still cannot look
   past MPLS labels (even after popping them) into the encapsulated
   packet.  Kernel datapath support is unchanged from earlier
   versions.

   Open vSwitch version 2.2 will be able to match, push, or pop up to
   3 MPLS labels.  Looking past MPLS labels into the encapsulated
   packet will still be unsupported.  Both userspace and kernel
   datapaths will be supported, but MPLS processing always happens in
   userspace either way, so kernel datapath performance will be
   disappointing.