[ovs-discuss] OpenVswitch and VLAN
leland at DEV.DISCPRO.ORG
Tue Sep 27 19:33:44 UTC 2011
Could this be somewhat related to an issue that we spotted recently in Xen
whereby traffic sent from the hypervisor node tagged the traffic with the
VLAN ID, but since that VLAN is also the native VLAN for the trunk-port, the
switch simply didn't tag it (assuming that the device knew how to deal with
native [untagged] frames). We worked-around the issue by ensuring that
tagging was set even for this "native" vlan on the physical switch side.
Wondering if it's related, that's all.
Le 27/09/2011 18:22, « Jesse Gross » <jesse at nicira.com> a écrit :
> On Tue, Sep 27, 2011 at 1:39 AM, Doude <doudouyam at gmail.com> wrote:
>> Ha yes, I miss that.
>> Here log you asked, in my test I worked on VLAN id 1001:
>> - OVS ping sender:
>> tun_id0 in_port2 tci(0) macaa:aa:00:00:01:12->ff:ff:ff:ff:ff:ff
>> type0806 proto1 tos0 ip10.0.0.1->10.0.0.2 port0->0, packets:50,
>> bytes:2100, used:0.610s, actions:set_tci(vid=1001,pcp=0),0,1
>> - OVS ping receiver:
>> tun_id0 in_port1 tci(0) macaa:aa:00:00:01:12->ff:ff:ff:ff:ff:ff
>> type0806 proto1 tos0 ip10.0.0.1->10.0.0.2 port0->0, packets:169,
>> bytes:9464, used:0.410s, actions:drop
> Well OVS is indeed receiving untagged packets. However, looking back
> at your original message, I see what the problem is now.
> The version of OVS that you are using is too old to support the vlan
> offloads that are present in the kernel packaged with Ubuntu. You'll
> have to upgrade to a newer upstream version of OVS - even though what
> you are using is packaged with the most recent version of Ubuntu, it
> was released by us more than a year ago.
> discuss mailing list
> discuss at openvswitch.org
More information about the discuss