This may not be an easy bug to find. The solution will likely be one or two lines of code somewhere. Here is a challenge if someone wants it. It would probably require some debug experience, setting up a device driver debug environment, and learning about npf.sys. Any takers?
Robert Thornthwaite Input/Output, Inc. -----Original Message----- From: Loris Degioanni [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2003 4:22 PM To: [EMAIL PROTECTED] Subject: Re: [WinPcap-users] WinPcap 3.0 - PacketSendPackets problem. I've spent *a lot* of time on this bug during summer holidays and I thought that it was fixed, but a tester reported me that it seems still present despite my fixes. Now I'm away from university for a couple of months, so I'm not able to work on it until december. However, I suppose that "some one need to debug problems out" doesn't necessarly means "loris needs to debug problems out": sources are available, and I'm sure there is somebody smarter than me that will be able to fix the bug immediately. Loris ----- Original Message ----- From: "Mike Dawn" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, October 10, 2003 3:40 AM Subject: RE: [WinPcap-users] WinPcap 3.0 - PacketSendPackets problem. Hi: We encounter this problems at beginning of WinPcap 3.0 alpha test. It never go fix. Using gigabit NIC card will cause memory corruptions in WinPcap drivers. Some one need to debug problems out. Mike -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2003 6:12 AM To: [EMAIL PROTECTED] Subject: [WinPcap-users] WinPcap 3.0 - PacketSendPackets problem. I have a problem while using PacketSendPackets function on gigabit ethernet. About 30% of packets have a broken content. I wrote test programs, sender and receiver, and made some tests. My configuration is: 1-st computer (sender): Windows 2000 Pro, 2G RAM, Intel PRO/1000 MT 2-nd computer (receiver): Windows 2000 Pro, 512M RAM, Intel PRO/1000 MT WinPcap ver. 3.0 Comparing files original and received1 00000410: FE 00 00000411: FF A0 00000412: 00 6F 00000413: 01 88 Comparing files original and received2 00000221: 10 00 00000222: 11 A0 00000223: 12 6F 00000224: 13 88 Comparing files original and received3 00000031: 22 00 00000032: 23 A0 00000033: 24 6F 00000034: 25 88 Looks like driver (winpcap?) replace some user data in buffer by integer value. This value is the same for all broken packets. I'm ready to give source code of this test's on request to [EMAIL PROTECTED] Also, I have problem whits PacketSetBuff function. On 512M RAM computer PacketSetBuff allow to set up to 12Mbyte buffer size, while on 2024M RAM computer PacketSetBuff NOT allow to set more then ~1Mbyte buffer. P.S. Sorry for my English, it is not my native language. ================================================================== This is the WinPcap users list. It is archived at http://www.mail-archive.com/[EMAIL PROTECTED]/ To unsubscribe use mailto: [EMAIL PROTECTED] ================================================================== ====================== This is the WinPcap users list. It is archived at http://www.mail-archive.com/[EMAIL PROTECTED]/ To unsubscribe use mailto: [EMAIL PROTECTED] ====================== ================================================================== This is the WinPcap users list. It is archived at http://www.mail-archive.com/[EMAIL PROTECTED]/ To unsubscribe use mailto: [EMAIL PROTECTED] ================================================================== ================================================================= This is the WinPcap users list. It is archived at http://www.mail-archive.com/[EMAIL PROTECTED]/ To unsubscribe use mailto: [EMAIL PROTECTED] =================================================================
