It's still not clear what exactly your setup is. Have you checked the README for changes to the VLAN Tab Packet Steering?
Todd Fujinaka Software Application Engineer Networking Division (ND) Intel Corporation todd.fujin...@intel.com (503) 712-4565 -----Original Message----- From: Gilboa Davara [mailto:gilb...@gmail.com] Sent: Thursday, May 19, 2016 8:28 PM To: Intel-E1000-devel <e1000-devel@lists.sourceforge.net> Subject: Re: [E1000-devel] i40e: PROMISC broken in 1.5.x, works just fine in 1.2.38. On Wed, May 18, 2016 at 6:19 PM, Gilboa Davara <gilb...@gmail.com> wrote: > Hello all, > > We are developing a (non-DPDK-based) security product that uses > multiple Intel Intel NICs to monitor high speed traffic via passive > taps. > We recently ported our in-kernel software to use the latest i40e > drivers (1.5.16/18) up from 1.2.38 and we are faced with an odd > problem: Moving device to promisc mode (via dev_set_promiscuity and/or > via ifconfig) no longer forces the hardware into > dumb-packet-capture-mode. (We do see 'device switched to promisc mode' > kernel log messages). > Looking at the driver's own performance counters in > i40e_update_vsi_stats (and ethtool -S) we see near-zero rx_packet > counters and no rx_dropped/rx_errors. > Placing a hook inside i40e_clean_rx_irq and confirms that the driver > is completely idle. > > As the title suggests, switching back to 1.2.38 solves the problem. > > - System(s): HP DL160, DL380 and DL560. > - OS / kernels: > * Fedora 23, Linux 4.4 and 4.5. > * CentOS 7.1. Linux 3.10 (RHEL). > - RSS: 9 per link. > - Link type / speed: QSFP+, 40GbE. > - Additional information (ethtool -i) follows > > Are we missing something? > > Thanks for the help, > - Gilboa Hello all, Short follow up. FWIW I've upgraded the NVM on all NICs to 4.5.3 to no avail. $ for DEVICE in pci1p0 pci1p1 pci2p0 pci2p1 pci3p0 pci3p1 pci4p0 pci4p1 ; do echo ---- ; echo device: $DEVICE ; ethtool -i $DEVICE ; done ---- device: pci1p0 driver: i40e version: 1.5.18 firmware-version: 4.53 0x80001dca 0.0.0 expansion-rom-version: bus-info: 0000:4a:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ---- device: pci1p1 driver: i40e version: 1.5.18 firmware-version: 4.53 0x80001dca 0.0.0 expansion-rom-version: bus-info: 0000:4a:00.1 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ---- device: pci2p0 driver: i40e version: 1.5.18 firmware-version: 4.53 0x80001dca 0.0.0 expansion-rom-version: bus-info: 0000:04:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ---- device: pci2p1 driver: i40e version: 1.5.18 firmware-version: 4.53 0x80001dca 0.0.0 expansion-rom-version: bus-info: 0000:04:00.1 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ---- device: pci3p0 driver: i40e version: 1.5.18 firmware-version: 4.53 0x80001dca 0.0.0 expansion-rom-version: bus-info: 0000:07:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ---- device: pci3p1 driver: i40e version: 1.5.18 firmware-version: 4.53 0x80001dca 0.0.0 expansion-rom-version: bus-info: 0000:07:00.1 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ---- device: pci4p0 driver: i40e version: 1.5.18 firmware-version: 4.53 0x80001dca 0.0.0 expansion-rom-version: bus-info: 0000:41:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ---- device: pci4p1 driver: i40e version: 1.5.18 firmware-version: 4.53 0x80001dca 0.0.0 expansion-rom-version: bus-info: 0000:41:00.1 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ 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 ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ 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