setting
unchanged, in the end we modified router setting a little bit.
Sent from my ASUS
原始郵件
寄件者：Paolo Lucente
傳送日期：Tue, 01 Mar 2016 02:15:17 +0800
收件者：pmacct-discussion@pmacct.net
主旨:Re: [pmacct-discussion] ?^??: ?^??: Multiple pmacct processes listening at
similar interface
ind of flow packet frame structure.
>
> ?q: pmacct-discussion <pmacct-discussion-boun...@pmacct.net> ?N?? fboehm
> <fbo...@aon.at>
> ?H??: 2016?~02??28?? 00:22
> ??: pmacct-discussion@pmacct.net
> ?D??: Re: [pmacct
Am 27.02.2016 um 13:06 schrieb itria30...@itri.org.tw:
Is there potential risk, such as packet lost to implement a daemon (or
modify pmacct) listen to both Netflow and sflow and split them? Libcap
is known of packet drop when CPU low (I might be wrong for that
community keep improving).
I think
Lucente
傳送日期：Fri, 26 Feb 2016 08:08:03 +0800
收件者：吳天健
副本：pmacct-discussion@pmacct.net
主旨:Re: [pmacct-discussion] Multiple pmacct processes listening at similar
interface
Hi TC,
Consider nfacctd and sfacctd do not use libpcap in order to read
the incoming NetFlow/IPFIX and sFlow packets
ente
> ???e?GThu, 25 Feb 2016 05:53:05 +0800
> ???gpmacct-discuss...@pmacct.net
> ?D??:Re: [pmacct-discussion] Multiple pmacct processes listening at similar
> interface
>
> Hi Franz,
>
> Yes, it's no problem if, in general, two processes running libpcap
> are bin
seen a commercial solution that can collect all flow protocol in a single
port , but don't how this implemented.
Sent from my ASUS
原始郵件
寄件者：Paolo Lucente
傳送日期：Thu, 25 Feb 2016 05:53:05 +0800
收件者：pmacct-discussion@pmacct.net
主旨:Re: [pmacct-discussion] Multiple pmacct processes
Hi Franz,
Yes, it's no problem if, in general, two processes running libpcap
are binding to the same interface. You can in fact not only have any
two pmacctd binding there, but also a pmacctd and a tcpdump, etc.
Cheers,
Paolo
On Tue, Feb 23, 2016 at 01:23:29PM +0100, fboehm wrote:
> Hi,
>
> I
Hi,
I couldn't find a definitive answer on the web regarding following
situation:
Is it technically ok if multiple pmacct instances listen to the same
interface via libpcap? The interface is in promiscuous mode and is
getting traffic via a mirrored switch-port.
I like it because I don't
