RE: [WinPcap-users] Problems with Usage of pcap_stats_ex() in WinPcap 3.0
Thanks Fulvio,
It appears that ps_capt, ps_sent and ps_netdrop is only compiled in if
the REMOTE #define is set. I do not presently have this set, as I do not
do any remote capturing.
Is there any reason why I cannot just set REMOTE, even though I do not
use the remote capture stuff ?
Regards
Jaco
-Original Message-
From: Fulvio Risso [mailto:[EMAIL PROTECTED]
Sent: 12 June 2003 07:02
To: [EMAIL PROTECTED]
Cc: Jaco de Wet
Subject: RE: [WinPcap-users] Problems with Usage of pcap_stats_ex() in
WinPcap 3.0
Hi.
-Original Message-
From: Jaco de Wet [mailto:[EMAIL PROTECTED]
Sent: mercoledì 11 giugno 2003 18.17
To: [EMAIL PROTECTED]
Subject: [WinPcap-users] Problems with Usage of pcap_stats_ex() in
WinPcap 3.0
Hi All,
I have previously been using pcap_stats_ex() as defined in WinPcap 3.0
alpha4 to collect and display statistics about a capture session. I
used
the counters ps_recv, ps_drop and bs_capt as defined in PCAP.H (See
below)
struct pcap_stat {
u_int ps_recv; /* number of packets received */
u_int ps_drop; /* number of packets dropped */
u_int ps_ifdrop;/* drops by interface XXX not yet
supported */
#ifdef WIN32
u_int bs_capt; /* number of packets that reach the
application */
#endif /* WIN32 */
};
I could not get this working with the new full release of WinPcap 3.0,
and further investigation revealed that the definition of the
pcap_stat
structure in PCAP.H has been modified, as shown below:
struct pcap_stat {
u_int ps_recv; /* number of packets received */
u_int ps_drop; /* number of packets dropped */
u_int ps_ifdrop;/* drops by interface XXX not yet
supported */
#ifdef REMOTE
#ifdef WIN32
//u_int bs_capt; /* number of packets that reach the
application */
#endif /* WIN32 */
u_int ps_capt; /* number of packets that reach the
application; please get rid off the Win32 ifdef */
u_int ps_sent; /* number of packets sent by the server
on the network */
u_int ps_netdrop; /* number of packets lost on the network
*/
#endif
};
thus causing the problems with the u_int bs_capt. I cannot find any of
these changes in the documentation. Can the developers help ?
The fact is that the name bs_capt was wrong, because of a typo. The
correct name is ps_capt (all other members begin with ps).
WinPcap 3.0 fixed this typo.
Chees,
fulvio
Regards
Jaco de Wet
==
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]
=
RE: [WinPcap-users] Building version 3.0 on Windows 2000
-Original Message- From: Luke Brennan [mailto:[EMAIL PROTECTED] Sent: giovedi 12 giugno 2003 3.46 To: [EMAIL PROTECTED] Subject: RE: [WinPcap-users] Building version 3.0 on Windows 2000 Hello Bruce, Have you installed Visual Studio .NET *and* you have VC6 installed too? I did that and of course, the latest SDK installed all the includes into VC7. When I tried to compile with VC++ 6.0 it complained about these things. VC6 still had the old .H files. Copy the .H files from the platforms\SDK subdir from VC7 into VC98 \include and things now compile. No, please. Do not copy (and overwrite) files. Simply change the VC6 settings (Tools - Options - Directories) in order to use the ones provided with platform SDK *before* the ones of the Visual Studio. This procedure is described when installing the platform SDK. Cheers, fulvio Luke -Original Message- From: Bruce Leidl [mailto:[EMAIL PROTECTED] Sent: Thursday, 1 May 2003 8:36 AM To: [EMAIL PROTECTED] Subject: [WinPcap-users] Building version 3.0 on Windows 2000 Hi there, I've been trying to build the 3.0 release on Windows 2000 but it's not working out for me because there are a lot IPv6 specific structures that don't exist in the networking header files on Win2K, I believe they are only present on XP. I tried removing the INET6 define from the project, but that didn't help at all. Has anyone else got this to work? Is there some simple solution to this problem? thanks, --brl == 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] ==
RE: [WinPcap-users] Problems with Usage of pcap_stats_ex() in WinPcap 3.0
-Original Message-
From: Jaco de Wet [mailto:[EMAIL PROTECTED]
Sent: giovedì 12 giugno 2003 9.06
To: Fulvio Risso; [EMAIL PROTECTED]
Subject: RE: [WinPcap-users] Problems with Usage of pcap_stats_ex() in
WinPcap 3.0
Thanks Fulvio,
It appears that ps_capt, ps_sent and ps_netdrop is only compiled in if
the REMOTE #define is set. I do not presently have this set, as I do not
do any remote capturing.
That's a bug.
It has already been fixed in our CVS.
Tomorro afternoon we'll release an experimental version of WinPcap (which
will eb able to compile on linux and BSD as well), which will have this
issue solved.
Basically, if WIN32 is defined, the REMOTE flag will be turned on by
default.
Cheers,
fulvio
Is there any reason why I cannot just set REMOTE, even though I do not
use the remote capture stuff ?
Regards
Jaco
-Original Message-
From: Fulvio Risso [mailto:[EMAIL PROTECTED]
Sent: 12 June 2003 07:02
To: [EMAIL PROTECTED]
Cc: Jaco de Wet
Subject: RE: [WinPcap-users] Problems with Usage of pcap_stats_ex() in
WinPcap 3.0
Hi.
-Original Message-
From: Jaco de Wet [mailto:[EMAIL PROTECTED]
Sent: mercoledì 11 giugno 2003 18.17
To: [EMAIL PROTECTED]
Subject: [WinPcap-users] Problems with Usage of pcap_stats_ex() in
WinPcap 3.0
Hi All,
I have previously been using pcap_stats_ex() as defined in WinPcap 3.0
alpha4 to collect and display statistics about a capture session. I
used
the counters ps_recv, ps_drop and bs_capt as defined in PCAP.H (See
below)
struct pcap_stat {
u_int ps_recv; /* number of packets received */
u_int ps_drop; /* number of packets dropped */
u_int ps_ifdrop;/* drops by interface XXX not yet
supported */
#ifdef WIN32
u_int bs_capt; /* number of packets that reach the
application */
#endif /* WIN32 */
};
I could not get this working with the new full release of WinPcap 3.0,
and further investigation revealed that the definition of the
pcap_stat
structure in PCAP.H has been modified, as shown below:
struct pcap_stat {
u_int ps_recv; /* number of packets received */
u_int ps_drop; /* number of packets dropped */
u_int ps_ifdrop;/* drops by interface XXX not yet
supported */
#ifdef REMOTE
#ifdef WIN32
// u_int bs_capt; /* number of packets that reach the
application */
#endif /* WIN32 */
u_int ps_capt; /* number of packets that reach the
application; please get rid off the Win32 ifdef */
u_int ps_sent; /* number of packets sent by the server
on the network */
u_int ps_netdrop; /* number of packets lost on the network
*/
#endif
};
thus causing the problems with the u_int bs_capt. I cannot find any of
these changes in the documentation. Can the developers help ?
The fact is that the name bs_capt was wrong, because of a typo. The
correct name is ps_capt (all other members begin with ps).
WinPcap 3.0 fixed this typo.
Chees,
fulvio
Regards
Jaco de Wet
==
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]
=
Re: [WinPcap-users] NPF version
On Mon, Jun 09, 2003 at 09:39:13AM +0200, Loris Degioanni wrote: Yes, my answer was that no IOCTL is currently provided to retrieve the driver version. Consider that packet.dll version is strictly related to the NPF version, since the driver and the dll are always installed toghether by the winpcap installer, so if you don't install the WinPcap binaries manually (a practice that we strongly discourage) the versions are granted to be aligned. In every case, different versions normally are not able to work together. That's one reason why I wanted to report a mismatch - if somebody complains about WinDump/Ethereal/Analyzer/whatever not working correctly, and the version message reports a mismatch between the driver and the packet.dll, or the packet.dll library and the WinPcap library, the reply can just be we don't support that, try un-installing all the versions you have installed, and re-install one and only one version. The driver at the moment doesn't provide any means to obtain the version number. Probably, an IOCTL could be added for this purpose. I underline the fact that no one that uses the winpcap installer will be able to have mismatching versions of NPF/packet.dll. Loris == This is the WinPcap users list. It is archived at http://www.mail-archive.com/[EMAIL PROTECTED]/ To unsubscribe use mailto: [EMAIL PROTECTED] ==
RE: [WinPcap-users] Problems with Usage of pcap_stats_ex() in WinPcap 3.0
Does winpcap support IP V6? For example I want to set the filter to ICMP with target
machine with IP V6 address, does it work?
Thank you.
Wei
-Original Message-
From: Fulvio Risso [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 12, 2003 2:18 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: [WinPcap-users] Problems with Usage of pcap_stats_ex() in
WinPcap 3.0
-Original Message-
From: Jaco de Wet [mailto:[EMAIL PROTECTED]
Sent: giovedì 12 giugno 2003 9.06
To: Fulvio Risso; [EMAIL PROTECTED]
Subject: RE: [WinPcap-users] Problems with Usage of pcap_stats_ex() in
WinPcap 3.0
Thanks Fulvio,
It appears that ps_capt, ps_sent and ps_netdrop is only compiled in if
the REMOTE #define is set. I do not presently have this set, as I do not
do any remote capturing.
That's a bug.
It has already been fixed in our CVS.
Tomorro afternoon we'll release an experimental version of WinPcap (which
will eb able to compile on linux and BSD as well), which will have this
issue solved.
Basically, if WIN32 is defined, the REMOTE flag will be turned on by
default.
Cheers,
fulvio
Is there any reason why I cannot just set REMOTE, even though I do not
use the remote capture stuff ?
Regards
Jaco
-Original Message-
From: Fulvio Risso [mailto:[EMAIL PROTECTED]
Sent: 12 June 2003 07:02
To: [EMAIL PROTECTED]
Cc: Jaco de Wet
Subject: RE: [WinPcap-users] Problems with Usage of pcap_stats_ex() in
WinPcap 3.0
Hi.
-Original Message-
From: Jaco de Wet [mailto:[EMAIL PROTECTED]
Sent: mercoledì 11 giugno 2003 18.17
To: [EMAIL PROTECTED]
Subject: [WinPcap-users] Problems with Usage of pcap_stats_ex() in
WinPcap 3.0
Hi All,
I have previously been using pcap_stats_ex() as defined in WinPcap 3.0
alpha4 to collect and display statistics about a capture session. I
used
the counters ps_recv, ps_drop and bs_capt as defined in PCAP.H (See
below)
struct pcap_stat {
u_int ps_recv; /* number of packets received */
u_int ps_drop; /* number of packets dropped */
u_int ps_ifdrop;/* drops by interface XXX not yet
supported */
#ifdef WIN32
u_int bs_capt; /* number of packets that reach the
application */
#endif /* WIN32 */
};
I could not get this working with the new full release of WinPcap 3.0,
and further investigation revealed that the definition of the
pcap_stat
structure in PCAP.H has been modified, as shown below:
struct pcap_stat {
u_int ps_recv; /* number of packets received */
u_int ps_drop; /* number of packets dropped */
u_int ps_ifdrop;/* drops by interface XXX not yet
supported */
#ifdef REMOTE
#ifdef WIN32
// u_int bs_capt; /* number of packets that reach the
application */
#endif /* WIN32 */
u_int ps_capt; /* number of packets that reach the
application; please get rid off the Win32 ifdef */
u_int ps_sent; /* number of packets sent by the server
on the network */
u_int ps_netdrop; /* number of packets lost on the network
*/
#endif
};
thus causing the problems with the u_int bs_capt. I cannot find any of
these changes in the documentation. Can the developers help ?
The fact is that the name bs_capt was wrong, because of a typo. The
correct name is ps_capt (all other members begin with ps).
WinPcap 3.0 fixed this typo.
Chees,
fulvio
Regards
Jaco de Wet
==
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]
=
RE: [WinPcap-users] Problems with Usage of pcap_stats_ex() in WinPcap 3.0
-Original Message- From: Jiang, Wei [mailto:[EMAIL PROTECTED] Sent: giovedì 12 giugno 2003 15.48 To: [EMAIL PROTECTED] Subject: RE: [WinPcap-users] Problems with Usage of pcap_stats_ex() in WinPcap 3.0 Does winpcap support IP V6? Yes. For example I want to set the filter to ICMP with target machine with IP V6 address, does it work? Yes. fulvio = This is the WinPcap users list. It is archived at http://www.mail-archive.com/[EMAIL PROTECTED]/ To unsubscribe use mailto: [EMAIL PROTECTED] =
