If you include bittypes.h, add the following definitions to your project:

SIZEOF_CHAR=1, SIZEOF_SHORT=2, SIZEOF_INT=4.

Look at the windump project for details.

Loris

----- Original Message -----
From: "Beatriz Silva" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 17, 2002 10:56 PM
Subject: [WinPcap-users] program to sniff packets


> Hi everybody !
>
> First of all, thanks Loris for all of your answers, they helped me a lot
: )
> But now I have another doubt:
>
> I copied the example program pcap_filter and now I am trying to extend it
to print some parts of the ethernet header (like in the tutorial of Martin
Casado).
> So the first thing I did was to copy the ethernet header definition:
>
> struct ether_header
> {
>   u_int8_t  ether_dhost[ETH_ALEN]; /* destination eth addr */
>   u_int8_t  ether_shost[ETH_ALEN]; /* source ether addr */
>   u_int16_t ether_type;         /* packet type ID field */
> } __attribute__ ((__packed__));
>
> But I could not find a library in Windows which defines the parameter
u_int8_t.
> Then, I found out in tcpdump code the file "bittypes.h" which defines this
u_int8_t but just including this file in my workspace does not help. There
is the variable "SIZEOF_CHAR" in the beginning of the file, which I could
not find where it comes from. Is it (SIZEOF_CHAR) defined when the config.h
file is created ? How can I get this config.h (I just can find config.h.in
and etc)?
> I found out then in Unix that u_int8_t is defined in the file
"sys\types.h".
> Why in "bittypes.h" the definition of u_int8_t is dependent on the value
of SIZEOF_CHAR and in the "sys\types.h" not ?
> I hope you could understand my question : ) I would be very glad if
somebody could answer to me.
>
> Thanks a lot !
>
> Beatriz.
>
>
> --
> __________________________________________________________
> Sign-up for your own FREE Personalized E-mail at Mail.com
> http://www.mail.com/?sr=signup
>
> Save up to $160 by signing up for NetZero Platinum Internet service.
> http://www.netzero.net/?refcd=N2P0602NEP8
>

Reply via email to