[ovs-discuss] 802.1 ad patch /patch/584074/

Thomas F Herbert thomasfherbert at gmail.com
Wed Feb 24 16:44:42 UTC 2016


On 2/22/16 5:20 AM, gayathri.manepalli at wipro.com wrote:
>
> Hi Arun,
>
> Please find my comments inline,
>
> 1. When I send untagged or ctagged packets on veth0, the tshark 
> capture on veth2 shows another tag being added with VLAN 100 as 
> expected. However, the tpid is "8100" rather than 88a8 as expected.
>
> //In our test bed we are using Spirent as traffic gen and we are able 
> to see tpid as “88a8”. Can you share which traffic generator and 
> capture tool you are using ?
>
> 2. When I try to send packets on veth2, I am not seeing any packets 
> come through to veth0.
>
> // If you want to send packets from veth2(trunk mode) to veth0 
> (trunk-qinq mode), you have to send tagged packet (with vlan id as 100 
> as per your below configuration) , otherwise packet will get dropped.
>
> 3. Also I would like to change the outer tag to 9100 instead of 88a8. 
> Is this possible? I can also make code changes if required.
>
> // Current implementation is based on IEEE standard 802.1ad(tpid 
> 88a8). However we have plan to make this configurable then 9100 can be 
> supported. Feel free to make necessary code changes to make this 
> configurable and share the source code.
>
I am currently working on the earlier version of my 802.1ad patch to add 
both TPIDs as well as CFI's to the flow structure in the user space 
patch. When this is accomplished, protocol numbers other then 88a8 and 
8100 should be functional.
>
> Thanks & Regards,
>
> Gayathri
>
> *From:*arun ganesh [mailto:arunganesh.j at gmail.com]
> *Sent:* Friday, February 19, 2016 1:24 PM
> *To:* discuss at openvswitch.org
> *Cc:* Manepalli S Gayathri (NEP) <gayathri.manepalli at wipro.com>; 
> Sanjeev Sharma (Cisco) <sanjeev.sharma15 at wipro.com>
> *Subject:* 802.1 ad patch /patch/584074/
>
> Hi,
>
> I included the patch https://patchwork.ozlabs.org/patch/584074/ into 
> openvswitch-2.4.0 and running the compiled image.
>
> I have configured the below, where veth0 and veth2 are 2 virtual 
> interfaces.
>
> [root at localhost ~]# ovs-vsctl show
>
> 92950bce-8b0f-41bc-b197-cd9ed432bb4b
>
>     Bridge "br0"
>
>         Port "veth2"
>
>             Interface "veth2"
>
>         Port "br0"
>
>             Interface "br0"
>
>                 type: internal
>
>         Port "veth0"
>
>             Interface "veth0"
>
> [root at localhost ~]#
>
> [root at localhost ~]#
>
> [root at localhost ~]# ovs-vsctl set port veth0 tag=100 vlan_mode=trunk-qinq
>
> The problems that I am seeing are below.
>
> 1. When I send untagged or ctagged packets on veth0, the tshark 
> capture on veth2 shows another tag being added with VLAN 100 as 
> expected. However, the tpid is "8100" rather than 88a8 as expected.
>
> 2. When I try to send packets on veth2, I am not seeing any packets 
> come through to veth0.
>
> Am I missing something here? Please clarify.
>
> 3. Also I would like to change the outer tag to 9100 instead of 88a8. 
> Is this possible? I can also make code changes if required.
>
> Regards,
>
> Arun
>
> 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
>
>
> _______________________________________________
> discuss mailing list
> discuss at openvswitch.org
> http://openvswitch.org/mailman/listinfo/discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20160224/4beaaa18/attachment-0002.html>


More information about the discuss mailing list