Nfsen is very outdated, and the official guides doesnt work on Ubuntu 22.04. Has anyone integrated nfsen-ng or another netflow/ipfix vizualiser with LibreNMS? Any guides?
I know of some other external tools such as elastiflow, but I was looking into having something integrated along with LibreNMS.
“nfsen-ng is an in-place replacement for the ageing nfsen.”
Requirements include rrdtool and php, which LibreNMS already uses.
I’ve used Elastiflow before, and it is very nice - but I have no idea how licenses would work. Also its running on top of an ELK cluster, which makes things a bit more complex just implementing that.
I was simply looking for the existing Billing plugin, but able to pin down per LAN-IP usage, and preferably a listing of that per timeperiod. So strange that such basic functionality doesn’t exist. Must say that even a solution like netflow is waaaay overkill for what most would need. Just a top listing of those local IPs that use the most data from/to the internet would be fine.
This tool: GitHub - neatbasis/bandwidthd: Ipv6 capable bandwidthd from http://sourceforge.net/projects/bandwidthd/ would suffice, were it not that this does not distinguish internal (LAN) traffic from internet traffic.
As far as I understand, Netflow analysis and SNMP polling (the main way LibreNMS works) are different things, it is difficult to put them together.
Moreover, I have seen in some networks with multiple routers that SNMP traffic may not match *flow traffic, and this is a headache for engineers.
Users who need netflow (especially enterprise users) create many monitoring objects, analyze traffic by GeoIP, autonomous systems, use *flow to protect against DoS/DDoS, etc. They usually use two separate systems, for monitoring and *flow analysis.
I am involved in the development of netflow/IPFIX/sFlow collector/analyzer GitHub - vmxdev/xenoeye: Lightweight Netflow/IPFIX collector and once wanted to integrate it in some form into LibreNMS.
But I do not understand how to do this.
Firstly, I do not know how to write plugins for LibreNMS.
Secondly, *flow collector does not know anything about your networks, does not know what exactly you want to see in reports, all this things will need to be configured.
It is easier to set up separate visualization of *flow traffic, for example in Grafana, create alerts for exceeding traffic by IP addresses and separately monitor networks using LibreNMS/SNMP.