Ntopng v3.0.0 released
-
Should be available shortly as a FreeBSD Port. IIRC, a native FreeBSD Port is required before the pfSense team can update the package for pfSense
https://svnweb.freebsd.org/ports/head/net/ntopng/
https://www.freshports.org/net/ntopng/ -
Lets hope so because as far as I can see it is already in the FreeBSD Port:
https://www.freebsd.org/cgi/ports.cgi?query=ntopng&stype=all
-
Looked what popped in shortly after my posting: http://pkg.freebsd.org/freebsd:10:x86:64/latest/All/ntopng-3.0.2017.06.05.txz
Freshports had it yesterday but there wasn't a compiled package/port to download when I looked
-
I think the ports are pulled into the pfSense FreeBSD ports repo every 3 months or so. Would be great if a special case could be made on this though, as it's a major version release so would be good to have it soon. :)
-
The ntopng package needs tuning.
It hogs way too much space and it doesnt seem to be a way to limit it easi.
-
i have it on overkill hardware
+1 on hopes for a quick pull into pfsense hate to wait to q3 packages
-
The ntopng package needs tuning.
It hogs way too much space and it doesnt seem to be a way to limit it easi.
I run ntopng on relatively basic hardware and using a RAM disc for the tmp/var folders (which is where the databases are held). I'm mainly interested in live data rather than historic, so I set the retention periods in preferences to 1 day - that keeps the storage requirements right down.
-
I run pfSense on powerful hardware but with ntopng I still have the problem that ntopng from time to time is not accessible.
When I try to connect to https://localhost:3000 I often receive a failure in connection but the pfSense service page shows that the service is running.
Hope this problem will be solved wit 3.0.0 where it says ""better FreeBSD support"
-
I run pfSense on powerful hardware but with ntopng I still have the problem that ntopng from time to time is not accessible.
When I try to connect to https://localhost:3000 I often receive a failure in connection but the pfSense service page shows that the service is running.
Hope this problem will be solved wit 3.0.0 where it says ""better FreeBSD support"
I too have the same problem, specially when access remotely (via dyndns), any tip?
-
Is there any news about this?
-
It's available in 2.4.0 and on 2.3.5 snapshots.
