Abodunrin, Akeem G wrote: > Intel E1G44ET NICs would drop this kind of "invalid" packet in the promisc > mode, > because length field in the packet is set to 846 but the packet length on the > wire is actually 842. > > In addition, Broadcom NICs did not allow the packets either, but raised an > error > flag that pushed onto the Wireshark, packets #2, 9, ... on the Broadcom > capture. > > Please check the "Expert Info" under "Length", the packet is reported with > error > message " Length field goes past the end of the payload". > > I hope that clarified the issue. If desired, we could provide you a patch > with > slight driver modifications that you could use to fix or verify the issue.
Yes, that completely resolves the question of why we weren't seeing these packets. Unfortunately, we do need to see them and we can't change the sender. Therefore, I'd very much appreciate the "slight driver modifications" that would allow that. Thank you for the analysis and response. -- Dave Close ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense.. http://p.sf.net/sfu/splunk-d2d-c1 _______________________________________________ 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
