Hi All,
I am trying to configure vlan stacking (802.1ad) to few ovs bridge ports, in
Normal mode bridge operation. I am using ovs-master code
Version 2.3.9 for my experiments.
I am seeing no support for stacked vlans both from the configuration interface
perspective and datapath as well.
I am trying to come up with the design and implementation of configuration
interface support for 802.1ad (ovs-vsctl) and also datapath support.
Currently as I understand ovs-vsctl vlan configuration has the following modes
defined in ovsdb: access, native−tagged, native−untagged, and trunk.
I have the following configuration in my mind for 1ad support.
1.Access port :
Adds C-VLAN ,does 802.1q tagging as usual, Ex: tag =10)
3.Trunk port without qinq support : On ingress by default
receives all vlan tagged traffic(single) , sends the same out of egress.
(double tagged traffic currently misbehaving)
4.Trunk port with qinq support : On ingress adds a
specific S-VLAN for a specific customer. On egress pops S-VLAN.
As I understand access port doesn’t require qinq support , so supporting the
same for trunk ports only
It would be really helpful , if you could let me know your suggestions and
comments towards my approach. Also let me know how the ovs community is
approaching towards
802.1ad, So that it will be in sync with ovs community thoughts.
Also I am seeing multiple patches for 1ad support in datapath, though few not
working for me. Please, let me know if any working patch is available that
would greatly save my
time in this experiment.
Thanks in Advance,
Uday
The information contained in this electronic message and any attachments to
this message are intended for the exclusive use of the addressee(s) and may
contain proprietary, confidential or privileged information. If you are not the
intended recipient, you should not disseminate, distribute or copy this e-mail.
Please notify the sender immediately and destroy all copies of this message and
any attachments. WARNING: Computer viruses can be transmitted via email. The
recipient should check this email and any attachments for the presence of
viruses. The company accepts no liability for any damage caused by any virus
transmitted by this email. www.wipro.com
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
