On 03/07/2014 04:27 AM, kiko wrote:
Hi Peter ,
I had the same issue.
Finally, I got access to a box with the same problem. I will report back
as soon, as I have more information.
- Peter
And I notice something different with your example.
In
Dear nfsen users,
I am currently setting up our first nfsen installation on debian wheezy.
The live profile is working fine, I am receiving netflow data from our
routers (c6500/SUP720 and ASR9k) and graphs are filling up / processing
and filtering works.
What does not work is an additional
Hello Chris,
I did what you suggested, but the alert never triggers. I put a low value of
10. I see some dstIP with higher than 10 flows, but it doesn’t work.
Any idea?
Pat
The information in this message, including in all attachments, is confidential
or privileged. In the event you have
Ok it’s working now, I had to change the default filter from “not any” to
“proto udp”
Now I’m getting this error when it tried to send an email
Mar 26 11:25:00 netflow01 nfcapd[22729]: Ident: 'RouterA' Flows: 12355,
Packets: 70331, Bytes: 5203913, Sequence Errors: 0, Bad Packets: 0
Mar 26
The problem is, software with compile time options is completely unsuitable
for that packaging. For nfsen to work, that package must be built with
nfprofile.
To prevent trouble (and because I run several different instances on the same
server and I use nginx with php-fpm instead of
Hi all,
Find appended a patch, which fixes the problem for not profiling the history
data correctly. The bug is triggered, when
setting ZIPprofile to 1 in nfsen.conf. A new NfSen release, which fixes some
more issues, especially Perl compatibility,
will be released soon.
Thanks Wim for your
