Cut it out with the CC to discuss-request, by the way. It makes no
sense at all and just causes a bounce back.
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
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?
Thanks Ben for some insights on userspace datapath.
I had a quick peek into the file, INSTALL.space and followed the instructions.
Its working fine for pushing a MPLS header for flows. i.e.,
sudo ovs-ofctl add-flow br0
in_port=1,actions=push_mpls:0x8847,set_field:100-\>mpls_label,output:2 -O
Op
On Fri, Feb 07, 2014 at 07:43:55AM -0800, Madhusudhan Kandadai wrote:
> Can you please let me know the differences between userspace datapaths
> and kernal datapaths?
INSTALL.userspace explains how to use the userspace datapath.
> With that being said, MPLS push,pop,match are happening at user sp
Hello,
Can you please let me know the differences between userspace datapaths and
kernal datapaths?
With that being said, MPLS push,pop,match are happening at user space data
paths. I appreciate if you can point me the documentation, or with examples to
get familiar with this stuffs.
Thanks
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 versi
Hello,
I am sure this is going to be the repeated question. But this time, I tried to
debug what exactly going on with my problem.
I have inserted a flow and it is mentioned below:
ovs-ofctl add-flow s1
in_port=1,ip,actions=push_mpls:0x8847,set_field:100-\>mpls_label,output:2 -O
OpenFlow13
T
