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]
=================================================================

Reply via email to