|
The function is implemented in Packet.dll, the sources are in
\winpcap\Packetntx\dll\packet32.cpp
It's my understanding that you implemented support for your
card directly in wpcap.dll. If so, the p->adapter field is a NULL/bogus
pointer, so there Packet API will receive a NULL/bogus pointer!
Have a nice day
GV
----- Original Message -----
Sent: Wednesday, October 17, 2007 6:29
AM
Subject: [Winpcap-users] Problems with
the modified wpcap.dll in Wireshark
Hello,
We have developed our device to capture ss7
traffic on a TDM link.
Once we start our device, we get this message.
" Couldnt set capture buffer size Size 1MB seems to be too high
for your machine
default is 1MB Any way capture started.
"
and it takes some time before the packets are being displayed on the
GUI.
As I heard it comes with the Win32-only pcap_setbuff() routine
not being set
up to handle add-on capture interfaces such as ours. As I saw
this is done by
the function PacketSetBuff(p->adapter,dim), which I
suspect a function to
change the driver behaviour, for which I do not have
access.
Where is this PacketSetBuff() written?
If its on user
mode and doesnt need the ddk, can I change it so that I can
overcome this
problem. Or any way I can overcome this! :-)
My next question is our
GUI freezes when a live capture is going, and we are
not able to stop the
live capture when we need. What could be the problem
for this? It keeps on
capturing data at some speed around 128kbps.
Kind regards
Varuna De Silva
_______________________________________________
Winpcap-users
mailing
list
Winpcap-users@xxxxxxxxxxx
https://www.winpcap.org/mailman/listinfo/winpcap-users
|
