On 11/06/2012 01:15 AM, Levy, Lior wrote: > This behavior/message occurs due to setting a "port" VLAN from the PF > side. Administratively VLAN can be set by the PF using the ip command > 'ip link set<ethx> vf<n> vlan<vlanID>'. When setting VLAN ID from > the VF/VM side port VLAN cannot be used.
Yeah, we figured that out...originally we weren't setting it from the PF side, just the VF. I've upgraded to the latest igb driver but still no dice. We've got tcpdump running on the bare VF devices (eth1) in both VMs. Trying to ping from the vlan device (eth1.42) to the vlan device in the other VM results in arps being sent out. The tcpdump on the tx eth1 shows vlan42, but on the rx side it doesn't. Is there something that can cause the internal switch to strip the vlan header? Chris ------------------------------------------------------------------------------ LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
