Hi Paolo,
On Mon, 3 Aug 2009, Paolo Lucente wrote:
Didn't act on it yet, being focused on some new features. My goal is to
do something about it in 0.12.0rc2. Basically it would be a fix for who
doesn't use an UTC clock on the system running pmacct. If there is
general interest around
On Tue, Aug 04, 2009 at 10:35:31AM +0100, Chris Wilson wrote:
Is any real-world system set to UTC? I'm certainly not going to run my
firewall (where I run pmacct currently) on UTC. All my logs would be
screwed up and much harder to interpret.
i tend to run all my servers in utc.
the logs
I notice with multiple interfaces that I get duplicate flows. If I recall
correctly a cisco router does netflow only on input while it seems pcap
captures both inbound outbound packets. My work around to filter out
the output flows was to use a pcap_filter such as:
!
daemonize: true
promisc:
Hi Stig,
Very briefly to confirm: a) you are correct, libpcap captures
both inbound and outbound traffic and b) the workaround you
have put in place not only makes sense but is also by far the
most efficient way to filter traffic out of pmacctd.
Cheers,
Paolo
On Tue, Aug 04, 2009 at 10:39:00AM
On 08/04/2009 04:35:31 AM, Chris Wilson wrote:
Is any real-world system set to UTC? I'm certainly not going to run
my
firewall (where I run pmacct currently) on UTC. All my logs would be
screwed up and much harder to interpret.
Setting the system clock to UTC is traditional in Unix,
