[ovs-discuss] vlan tagging broken - kernel 3.10 compatibility issue

Jesse Gross jesse at nicira.com
Fri Sep 6 00:26:25 UTC 2013


Can you please provide the information that I originally requested (below)?

On Thu, Sep 5, 2013 at 1:15 PM, Andrey Korolyov <andrey at xdel.ru> wrote:
> Hello,
>
> Observing the same issue in quite simple topo:
>
>     Bridge "oswbr0"
>         Port "oswbr0"
>             Interface "oswbr0"
>                 type: internal
>         Port "vnet0"
>             tag: 100
>             Interface "vnet0"
>         Port "vnet1"
>             tag: 5
>             Interface "vnet1"
>         Port "bond0"
>             Interface "bond0"
>     ovs_version: "1.10.0"
>
> bond0 is a regular linux bond configured as a OVS port. There is
> simply no tagged traffic on this port but untagged works just fine.
>
>
> Tested on both 3.10 ``stock'' module and on
> 7395c05254df87ce52b37b04478e802befd799d9. Any suggestions are very
> appreciated since I`m bounded with 3.10 and can not afford downgrade.
>
>
> On Tue, Aug 20, 2013 at 5:10 AM, Jesse Gross <jesse at nicira.com> wrote:
>> On Mon, Aug 19, 2013 at 2:07 PM, Ruß, André <andre.russ at hybris.com> wrote:
>>> Hi,
>>>
>>>
>>>
>>> I run two bridges on my openvswitch (ovsbr0, ovsbr1) both have redundant
>>> ports (bond0, bond1 with lacp) since the port groups have different
>>> performance (1gbs and 10gbs). Multiple internal interfaces are connected to
>>> the bridges and get network traffic assigned based on the vlan tag.
>>>
>>> Since version 3.10 of the kernel only works with the first bridge (ovsbr0)
>>> as expected the second one gets not tagged traffic (untagged works fine!).
>>>
>>> It makes no difference if I use the default kernel module or the upstream
>>> datapath module.
>>
>> Can you run ovs-dpctl dump-flows and tcpdump when you have some vlan
>> traffic running through each of the bridges and send that and the
>> output of ovs-dpctl show?
>> _______________________________________________
>> discuss mailing list
>> discuss at openvswitch.org
>> http://openvswitch.org/mailman/listinfo/discuss



More information about the discuss mailing list