Thanks for the answers, On Mon, Jun 24, 2013 at 5:03 PM, Ben Pfaff <b...@nicira.com> wrote:
> On Mon, Jun 24, 2013 at 03:56:31PM -0700, Alex Wang wrote: > > 1. What is usually the bug in the buggy driver? How can using > vlan-splinter > > avoid that? I'm a bit confused here, since the "vlandev.c" code still > talks > > to linux device driver (e.g. when creating ADD_VLAN_CMD) via the "ioctl" > > call. > > ovs-vlan-bug-workaround(8) has a lot of information: > > ...... This is very helpful. Also, Do you which file I should check to see how packet (with vlan header) arrived on a trunk port is mapped to corresponding vlandev port? > > 2. If vlan-splinter is not used, the vswitchd will learn the vlan > > configuration from the packets and record them in the learning table. > right? > > If the driver is buggy, then the packets won't have the right > information and vswitchd won't be able to compensate for it. This makes sense after reading the FAQ and ovs-vlan-bug-workaround manual. Thanks
_______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
