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

Reply via email to