nope.. this wasn't on OVS.. it was on the native xen bridge... but if OVS only supports native since yesterday, then the Xen issue seems logical :)
Leland Le 27/09/2011 22:11, « Jesse Gross » <je...@nicira.com> a écrit : > On Tue, Sep 27, 2011 at 12:33 PM, Leland Vandervort > <lel...@dev.discpro.org> wrote: >> >> Hi Jesse, >> >> >> 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. > > You're saying that Open vSwitch wasn't doing tagging because of a > native vlan? Open vSwitch didn't support native vlans until yesterday > afternoon, so unless you are running a very bleeding edge version, I > think you have a configuration error. Perhaps you configured the > trunk port as an access port. _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
