Re: [WinPcap-users] I got a Blue Screen of Death on my W2K Server while using WinPcap ver 2.3

[Denis Bujoreanu]

Well I saw that the export section, which interests me the most, of the 2.3 version differes from that of the 3.0a - obviously it has some more functions exported, but to my surprise some functions are also missing !!! Namely PacketResetAdapter and PacketWaitPacket which kinda renders the backward compatibility null. But still, this doesn't bother me cause I don't use the missing functions, what bothers me is that now the PacketGetAdapterNames is different, I mean I get different info from the driver when calling for the adapter names which doesn't scale well in my app and I don't quite "get it" why. After all the adapter name doesn't change, right? I'll take a closer look at the examples.   My card is a plain ethernet (Accton EN2242 100Mbps) which works flawlessly with ver 2.3 on capture, but if I try to send packets I get the BSD.   I'm using the packet API cause the pcap API is "too simple" and too high up in the stack and from the pcap source I saw that what I do in my app is the same as pcap does, of course not as efficient but performance is not a big concern now, I need functionality first and then speed. One other reason I use the packet API is that in order for me to use the pcap API I'd have to port a lot of data structures and types. I know there's Lars's translation to Delphi for the pcap headers and types but I started using WinPcap before I knew about Lars's work and is too much hassle to switch to pcap now, especially since I get what I need from packet API. ----- Original Message ----- From: Gianluca Varenni To: [EMAIL PROTECTED] Sent: Monday, September 09, 2002 04:39 PM Subject: Re: [WinPcap-users] I got a Blue Screen of Death on my W2K Server while using WinPcap ver 2.3 Well, WinPcap 3.0 is backward compatible with 2.3. I suggested you to wpdpack 3.0a since we have corrected some bugs in the examples, and we have added a brand new HTML documentation and tutorial.   Regarding the crashes, on which network adapter are you using winpcap to send packets? Is it ethernet or PPP? Or anything else?   GV   PS. Why are you using the packet API? We usually suggest users to use the pcap API, which we think is much more simple, and yet powerful.     ----- Original Message ----- From: Denis Bujoreanu To: [EMAIL PROTECTED] Sent: Monday, September 09, 2002 3:12 PM Subject: Re: [WinPcap-users] I got a Blue Screen of Death on my W2K Server while using WinPcap ver 2.3 well, I don't use the wpcap library (u know... pcap_open_live and stuff), I use only the functions exported by the packet.dll   I have both 2.3 and 3.0a but the packet.dll doesn't seem to know about all the functions from ver. 2.3...how come? isn't there a backward compatibility? what do you mean by upgrading the wdpack? I've donwloaded both versions couple of weeks ago...   ----- Original Message ----- From: Gianluca Varenni To: [EMAIL PROTECTED] Sent: Monday, September 09, 2002 04:03 PM Subject: Re: [WinPcap-users] I got a Blue Screen of Death on my W2K Server while using WinPcap ver 2.3 Try winpcap 3.0alpha (remember to upgrade the developers' pack, too).   GV   PS. What do you mean by "I use Packet.dll and packet.sys and do not go through the API"?   ----- Original Message ----- From: Denis Bujoreanu To: [EMAIL PROTECTED] Sent: Monday, September 09, 2002 2:18 PM Subject: [WinPcap-users] I got a Blue Screen of Death on my W2K Server while using WinPcap ver 2.3 Hi,   I wrote an app that uses WinPacap ver. 2.3 (I use Packet.dll and Packet.sys and do not go through the API) to capture packets and if the TCP port matches a certain value than it writes a new packet that closes the connection (it's not a DoS tool, it's ment to be a intrusion prevention and access control tool so don't bite my head off yet). Form time to time I get a STOP fatal error on my W2K Server, the message error was that the irq was less or not equal to...or something like that, it was acompanied by a blue screen and a memory dump). I read in a previous post that this problem is not a singularity and that it has been fixed. Could it be that I am doing something worng (i.e try to write while reading or something like that?) I did take some precautions in my app so I don't step over my own toes (a flag that is set when I read and prevents my write to occur) but this thing still occured.