- Original Message -
From: "Alexander Dupuy" <[EMAIL PROTECTED]>
To:
Sent: Monday, December 10, 2007 10:42 AM
Subject: Re: [tcpdump-workers] [PATCH] enable memory mapped access to
ethernet device for linux
Guy Harris asked:
How does pcap_setbufsize() differ f
Guy Harris asked:
How does pcap_setbufsize() differ from pcap_setbuff()?
The WinPcap pcap_setbuff function is defined as:
int pcap_setbuff(pcap_t *p, int dim);
I declared it as follows:
extern int pcap_setbufsize(pcap_t *p, int bufsize, char *errbuf);
extern int pcap_getbufsize(pcap_t *p, ch
- Original Message -
From: "Guy Harris" <[EMAIL PROTECTED]>
To:
Sent: Thursday, December 06, 2007 4:09 PM
Subject: Re: [tcpdump-workers] [PATCH] enable memory mapped access to
ethernet device for linux
There's also an issue that with the ringbuffer, the init
[I sent this from my other account but it seems not to have gone through;
resending and apologies if you receive it twice.]
Paolo Abeni writes:
It does not use environment variables to control the memory mapped ring
parameters; instead the requested snap len is used: the low order bytes
are used
On Dec 6, 2007, at 9:54 AM, Alexander Dupuy wrote:
Paolo Abeni writes:
It does not use environment variables to control the memory mapped
ring
parameters; instead the requested snap len is used: the low order
bytes
are used to select the ring frame size and the high order bytes are
used
t
Paolo Abeni writes:
It does not use environment variables to control the memory mapped ring
parameters; instead the requested snap len is used: the low order bytes
are used to select the ring frame size and the high order bytes are used
to select the ring frame number. If the high order bytes is
entually create a new pcap_open_live_mmap() function)?
Have a nice day
GV
- Original Message -
From: "Paolo Abeni" <[EMAIL PROTECTED]>
To:
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, December 05, 2007 3:11 AM
Subject: [tcpdump-workers] [PAT
hi list,
Following the discussion about the memory mapped access for Linux, I
tried to rework some existing code (originally independently created by
Simon Patarin and Phil Wood) to enable this functionality with the
minimum impact on the current pcap code.
It does not use environment variables
