it's the modified version that comes with pf_ring.
actually the problem solved. apparently pf_ring before revision 4498 has this
problem (on some systems?) which is solved in 4498 or newer revisions (mine was
4494). i upgraded my pf_ring source from svn to latest (4521) and problem
solved
(alo
On Mar 8, 2011, at 1:15 AM, M. V. wrote:
> now, when i use tcpdump which is compiled with libpcap-pf_ring to capture
> traffic,
Is that standard tcpdump, or Luca's modified tcpdump (which is part of the
PF_RING stuff)?
If it's the standard tcpdump, what happens if you pass it the argument "-s
On Mar 7, 2011, at 4:32 AM, Miroslav Lichvar wrote:
> here is a patch fixing some typos.
Thanks. Checked into the trunk and 1.1 branch.
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.
On Mar 3, 2011, at 9:01 AM, Schemmel, Hans-Christoph wrote:
> this is the detailed description of the data format.
>
> LINKTYPE_MUX27010
OK, I've assigned 236 as LINKTYPE_MUX27010 and DLT_MUX27010.
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.
Hi Fabian, thanks for the link to your thesis. That's a well-put together and
very informative document.
I specially liked figure 2.2 (conceptual diagram of the Linux Socket Filter for
incoming packets).
In that figure, I see that any packet arriving at the "packet_input_queue" is
sent towar
hi,
in order to boost capturing performance, i installed PF-Ring for libpcap on
Debian-6.0 using the link below. i got latest version of pf-ring from svn, and
recompiled my intel-card's driver to support pf_ring. i didn't get any error or
problem during the process.
http://www.ntop.org/blog/?p
