We had an issue where our Intel X520-SR2 was dropping VLAN tagged traffic in 
promiscuous mode.  I am no driver developer and have a rudimentary knowledge of 
linux kernels, so I took a hammer to the issue and got VLAN tagged traffic to 
show up by making the following modifications to the ixgbe-3.9.15 source and 
creating a new ixgbe.ko from that.


=====

--- ixgbe_main.c.orig    2012-05-23 18:31:34.000000000 +0000
+++ ixgbe_main.c    2012-05-23 19:12:13.000000000 +0000
@@ -4227,17 +4227,7 @@
         ixgbe_irq_enable(adapter, true, true);
 #endif
 #ifdef HAVE_8021P_SUPPORT
-#ifdef HAVE_VLAN_RX_REGISTER
-    bool enable = (grp || (adapter->flags & IXGBE_FLAG_DCB_ENABLED));
-#else
-    bool enable = !!(features & NETIF_F_HW_VLAN_RX);
-#endif
-    if (enable)
-        /* enable VLAN tag insert/strip */
-        ixgbe_vlan_stripping_enable(adapter);
-    else
-        /* disable VLAN tag insert/strip */
-        ixgbe_vlan_stripping_disable(adapter);
+    ixgbe_vlan_stripping_disable(adapter);
 
 #endif
 }
@@ -4253,7 +4243,7 @@
      */
     ixgbe_vlan_rx_add_vid(adapter->netdev, 0);
 #ifndef HAVE_8021P_SUPPORT
-    ixgbe_vlan_stripping_enable(adapter);
+    /* ixgbe_vlan_stripping_enable(adapter); */
 #endif
     if (adapter->vlgrp) {
         u16 vid;


=====

What is the proper way to disable VLAN stripping while in promiscuous mode?  Is 
it as simple as a modprobe ixgbe option that I'm missing or something else?

Thanks,
Angelo
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
E1000-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit 
http://communities.intel.com/community/wired

Reply via email to