Michael Krueger wrote:
On Tue, 22 Jan 2008 19:47:24 +0100, Rick Jones <[EMAIL PROTECTED]> wrote:
How many processors do you have, are interrupts from each NIC going
to seperate processors/cores/whatever (show us the output of
/proc/interrupts), and have you bound each tcpdump to its
corresp
Michael Krueger wrote:
On Tue, 22 Jan 2008 19:47:24 +0100, Rick Jones <[EMAIL PROTECTED]> wrote:
How many processors do you have, are interrupts from each NIC going
to seperate processors/cores/whatever (show us the output of
/proc/interrupts), and have you bound each tcpdump to its
corresp
On Tue, 22 Jan 2008 19:47:24 +0100, Rick Jones <[EMAIL PROTECTED]> wrote:
How many processors do you have, are interrupts from each NIC going to
seperate processors/cores/whatever (show us the output of
/proc/interrupts), and have you bound each tcpdump to its corresponding
NICs interrupt C
On Tue, 22 Jan 2008 19:47:24 +0100, Rick Jones <[EMAIL PROTECTED]> wrote:
How many processors do you have, are interrupts from each NIC going to
seperate processors/cores/whatever (show us the output of
/proc/interrupts), and have you bound each tcpdump to its corresponding
NICs interrupt C
How many processors do you have, are interrupts from each NIC going to
seperate processors/cores/whatever (show us the output of
/proc/interrupts), and have you bound each tcpdump to its corresponding
NICs interrupt CPU?
rick jones
-
This is the tcpdump-workers list.
Visit https://cod.sandelma
Hi,
we try to build a capture daemon using pcap lib. It does work great on a
single NIC if running alone, but if started twice on different NICs (eth0
& eth1) it seems that somehow they interfere in such way that capturing is
slowing down and pcap_stat does report dropped packets.
The same
