What happened to this package NTOP, bandwidth
-
Hi Guys
Well, Does the new version will be ntop, bandwidth packages
-
We are working to get ntopng back, it was removed from the FreeBSD ports tree because it would not compile with a current version of one of its dependencies. Not sure of an ETA, hopefully before too long though.
-
From the perspective of the dev everything has been done already:
https://github.com/ntop/ntopng/issues/297#issuecomment-198243140
-
From the perspective of the dev everything has been done already:
https://github.com/ntop/ntopng/issues/297#issuecomment-198243140
The changes in ntopng itself, yes, the port still needs work to get it back in. Renato (rbgarga on that thread, who works here) will get it back into FreeBSD ports when time permits.
-
I've upgraded to the 2.3 RC, and all seems to work fine for me - thank you for all your hard work on this.
I was using ntopng under 2.2.x so look forward to having it back when time permits.
Thanks again.
-
… not chasing in any way, but I noticed that ntopng is not mentioned on the bugtracker as one of the packages under development - https://redmine.pfsense.org/issues/5568
Given the intention seems to be to bring it back when time permits, should it be on a bugtracker ticket anywhere please?
-
In case it helps, it looks like the compilation and linking issues have been overcomme in the context of building for pfSense 2.3:
http://www.gossamer-threads.com/lists/ntop/users/40434
-
Any news on this?
-
Guys, ntopng was fixed and approved for FreeBSD 10.1 more than a month ago.
Why this package still not in the pFsense?
I'm think that a lot of people looking forward for this to be done.
Any suggestions when ntopng will be available again? -
The port is still broken on FreeBSD: https://www.freshports.org/net/ntopng/
I hear it's very, very close though.
-
thank you for updating.
currently the only reason i am not upgrading yet . detailed stats provided by NTOP is always requested by management - but they mostly work through murphy to request it at the exact times that i dont have it available :P
have however played around with 2.3, and it looks really really really tempting!
-
The port is still broken on FreeBSD: https://www.freshports.org/net/ntopng/
I hear it's very, very close though.
If I understand that page correctly, it was restored on May 28th?
Does that mean we will see it in pfSense soon?
-
It's available on the development branch of pfSense (2.3.2).
If you upgrade to that, then look in the packages manager, it will be listed.
There's still a few niggles with ntopng (see here https://redmine.pfsense.org/issues/6443#change-27554), but I'm using it without any significant problems nonetheless.
-
Hey…
Any new about this ? -
ntopng is available under the current 2.3.2 development builds. 2.3.2 is expected to be released this week sometime, so everyone will be able to install both the new version of pfSense and the ntopng package.
I don't know anything about bandwidthd.
Also available when 2.3.2. hits will be a "Traffic Totals" package that is based on vnstat, providing hourly, daily, and monthly traffic totals for interfaces in both graph and table forms.
-
how do I report an issue with this package? https://pfsense:3000/ doesnt work but http://192.168.1.1:3000/ does
-
Start a fresh thread. But that may not have anything to do with the package.
-
Yeah, not sure how you not being able to resolve pfsense to an IP address is related to a fault with the package. Fix your DNS.
-
I'm pretty sure mermen's issue is a defect with the pfSense package for ntopng. The core issue is that the current package does not support use of HTTPS. If you are using HTTPS for the webgui you cannot access ntopng by hostname because of HSTS. Only HTTP by IP address will work.
This is discussed here:
https://forum.pfsense.org/index.php?topic=110026.msg643065#msg643065
There is an outstanding PR for the pfSense package for ntopng to address this.
[edited for politeness and clarity]
