hello,
on Thu 1/3/2008 10:26 AM Guy Harris wrote:
> Presumably if pcap_open_live() supplies a very large snapshot length,
> the attempt to allocate the ring buffer will fail if the ring buffer
> would be too large.
Currently the whole ring size is bounded to 4M, which seams a rasonable defaul
Paolo Abeni wrote:
- in the previous version of the patch, the capture snapshot was
incorrectly bound to 0x; this don't happen any more.
Presumably if pcap_open_live() supplies a very large snapshot length,
the attempt to allocate the ring buffer will fail if the ring buffer
would be to
Luca Deri wrote:
This function is the same as pcap_next with the difference that a buffer
+ buffersize is added. This allows libpcap not to use the shared buffer
(e.g. allocated in pcap_open_xxx) so that replacing in applications
calls of pcap_next with calls to pcap_next_pkt adds reentrancy w
hello,
On Thu, 2008-01-03 at 01:29 +0100, Luca Deri wrote:
> > Here handle->buffer refers to a memory mapped kernel buffer, which
> > holds
> > the USB Request Blocks and related meta-data. To make the patch work
> > is
> > necessary to perform a memcpy from the kernel buffer to the user
> > p
