Hi Team , We all know that ovs supports 4 types of port configuration .
1. Access 2. Trunk 3. Native-tagged 4. Native-untagged Through access port configuration we can achieve 802.1q by adding normal flow(Not Openflow) ,we all know that when ovs is configured with normal flow(default), ovs bridge acts as a legacy bridge. We are seeing no support for 802.1ad to implement provider-edge bridging. In an effort to implement the same in ovs and ovs-dpdk, we have written our own code to realize 802.1ad (Q-in-Q) . For this We have introduced a new vlan_mode as "trunk-qinq" . When you configure a phy port added to ovs as "trunk-qinq" , upon receiving cvlan tagged/untagged traffic it adds outer vlan header with specific outer vlan ID ; on egress(other side of Provider) it removes the outer vlan header and send it out . Our code changes include control plane and datapath changes. We want to contribute the same to the openvswitch . Please , let me know whom to approach regarding reviews. All comments are appreciated. Regards, 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
