There aren't enough details here. Can you tell us the exact steps you used for configuring the VLANs on the host and guest?
Thanks. Todd Fujinaka Software Application Engineer Networking Division (ND) Intel Corporation todd.fujin...@intel.com (503) 712-4565 -----Original Message----- From: Madhur Sethi [mailto:mad...@attivonetworks.com] Sent: Friday, October 03, 2014 5:12 AM To: 'e1000-devel@lists.sourceforge.net' Subject: [E1000-devel] igb 5.0.3-k driver doesnt pick up vlan tagged packets when using with openvswitch Hey Guys, It seems there is an issue with the igb drivers not being able to receive VLAN tagged traffic when used with openvswitch. I am on Centos 6.5 with the following kernel: 3.10.51-1.el6.elrepo.x86_64 I have the following intel driver in my setup. [root@XXX ~]# ethtool -i eth1 driver: igb version: 5.0.3-k firmware-version: 1.80, 0x00000000 bus-info: 0000:05:00.1 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no [root@XXX ~]# lspci | grep Ethernet 02:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) 02:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) 02:00.2 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) 02:00.3 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) 04:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) 04:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) I use eth1 on the DOM-0 for physical connectivity to my vm via openvswitch and an ip address is configured on the vm. When I try to ping another machine in the same network with vlan 5 , it seems that the arps are going out but the nic doesn't pick up the returning arps even though the other end is duly replying to the arps. [root@XXX ~]# tcpdump -i eth1 -ne arp tcpdump: WARNING: eth1: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes 16:30:13.035965 52:54:00:3c:77:f5 > Broadcast, ethertype 802.1Q (0x8100), length 46: vlan 5, p 0, ethertype ARP, Request who-has 2.2.2.2 tell 2.2.2.3, length 28 16:30:14.038195 52:54:00:3c:77:f5 > Broadcast, ethertype 802.1Q (0x8100), length 46: vlan 5, p 0, ethertype ARP, Request who-has 2.2.2.2 tell 2.2.2.3, length 28 I can see the arps being responded to on the other end. Can you guys help with this? Regards, Madhur ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ 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
