On Sep 23, 2007, at 9:08 PM, Varuna De Silva wrote:
On 9/23/07, Guy Harris <[EMAIL PROTECTED]> wrote:
If you're modifying libpcap to support a new type of capture, you
don't
write the callback function,
I am doing this for my device to be supported by wireshark. As I
understand
I dont
On 9/23/07, Guy Harris <[EMAIL PROTECTED]> wrote:
>
> Varuna De Silva wrote:
>
> Yes, the callback function is in the higher-layer software that uses
> libpcap/WinPcap. tcpdump, for example, has two callback functions that
> write raw packet data to a capture file and one callback function that
>
On 9/23/07, Guy Harris <[EMAIL PROTECTED]> wrote:
>
> Varuna De Silva wrote:
>
> > 1. what is really meant by the callback routine, what does it do? How
> > should I write this function?where should this be written. please be
> kind
> > to guide me to starting place. my idea is that it is the highe
Varuna De Silva wrote:
> 1. what is really meant by the callback routine, what does it do? How
> should I write this function?where should this be written. please be kind
> to guide me to starting place. my idea is that it is the higher layer sw
> which makes use of libpcap.
Yes, the callback fun
Hi all,
With regard to one of my earlier messages, I got a comprehensive reply by
Guy.
and it says in one point regarding the _read() function on
pcap-.cfile as
below,
" read_op should point to a routine that takes, as an argument, a
pointer to a pcap_t, a count, a pointer to a callback