But we always appreciate the help Ben! Greg,
We need to know the exact PCI Device ID'S of the HW. You can get this by giving us the output from 'lspci -nn' or 'lspci -vv'. We need to know the exact devices you are using. To get the stats from the HW you can use 'ethtool -d <ethx>' where ethx is the interface that you are trying to get the stats for. Like "eth0" for example. The network stats can be viewed view 'netstat -s'. Between the 2 commands you should be able to see where the packets are being dropped. Cheers, John > -----Original Message----- > From: Ben Greear [mailto:[email protected]] > Sent: Friday, June 24, 2011 4:18 PM > To: Greg Hupf > Cc: Ronciak, John; [email protected] > Subject: Re: [E1000-devel] Intel(R) Gigabit ET Quad Port Server Adapter > does not work with PROFINET > > On 06/24/2011 04:05 PM, Greg Hupf wrote: > > Hello John, > > > > Thanks for the reply. The device ID is 'E1G44ETBLK' (i.e. Intel > > Gigabit ET Quad Port Server Adapter E1G44ET with the 82576 > > controller). We are also having the same problem with the Intel > > adapters located on the motherboard (with the 82575EB controller). > > > > All the packets are received correctly in promiscuous mode. But > > without promiscuous mode some of the PROFINET packets are dropped > > (e.g. packets from managed PROFINET switches are received correctly, > > but packets from PROFINET bus couplers are dropped). > > > > We only seem to have this problem with Intel NICs that use the > '82575/6' > > controller and/or the 'igb' driver. We tried to do some investigation > > using wireshark. I can provide capture files if you think it would be > > helpful. Otherwise, I'll see if I can determine if it is the HW or > the > > stack that is dropping/filtering the packets. Thanks for the help, I > > appreciate your cooperation. > > If you are using the igb driver in the Linux kernel, as opposed to one > you download from Intel's site, you might try this patch: > > http://patchwork.ozlabs.org/patch/82675/ > > I had to add this to my setup to get it to handle MTU sized VLAN > packets when no VLANs were configured on the NIC. > > I'm not sure if the out-of-tree driver has the same issue or not. > > Note that I do not work for Intel, nor do I know a great deal about > their NICs/drivers. > > Thanks, > Ben > > -- > Ben Greear <[email protected]> > Candela Technologies Inc http://www.candelatech.com ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ 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
