Ntopng update?
-
https://xx.xx.xx.xx:3000
Script "/usr/local/share/ntopng/scripts/lua/login.lua" returned an error:
/usr/local/share/ntopng/scripts/lua/login.lua:11: attempt to call global 'sendHTTPContentTypeHeader' (a nil value)not working
-
I clicked the download update just to see what would happen…it locked up WGUI...I had to reboot the machine.
-
Bump… Any work on when this might be updated to 3.2? Or is there a way to turn off the update notice in the interface?
-
madpilot78 is the maintainer and normally kindly does a pull request to bring the updated source into the ports tree on github.
I couldn't immediately see his username on this forum though otherwise I would have cc'd him on this thread.
-
Nobody here by that nick.. there is a madpilot but no posts and not even logged in since 2011 ;)
-
Thanks. I've e-mailed him at his FreeBSD email address: https://www.freshports.org/net/ntopng/
-
… I've had a response:
Unuckily pushing to the pfsense ports tree does not depend on me.
They import the FreeBSD ports tree from time to time. They branch from
it at release time. Looks like their policy is to only branch with a new
dot release. I have no say in such policy not being part of the pfsense
project, I am a committer for the FreeBSD project.The pfsense project has ports in the tree for the user interfaces of the
supported packages, and I pushed there some UI functionality in the
past, but that is unrelated to their policy for importing updates to the
FreeBSD ports.You best bet is to push with the pfsense guys via bug reports or on
their forums.So I'm not sure who looks after bringing updated versions of ntopng across from FreshPorts? Looking at the actual ntopng package in pfSense (as opposed to the port), it looks like jim-p and doctornotor contribute to that (see https://github.com/pfsense/FreeBSD-ports/commits/devel/net/pfSense-pkg-ntopng). Not sure if they might know how the updated versions get pulled across. I recall reading that the process of pulling the ports from FreshPorts (not just ntopng) was automatic, and happened quarterly. Not sure if that's right or not.
Perhaps the best route is to add a feature request into the pfSense bugtracker? I've added one here: https://redmine.pfsense.org/issues/8241
-
… The todo request on the bug tracker has been rejected. There's an automatic quarterly update process whereby updates to all the ports (not just ntopng) are pulled across. So I guess we'll have to wait for ntopng to be updated as part of that
-
… The todo request on the bug tracker has been rejected. There's an automatic quarterly update process whereby updates to all the ports (not just ntopng) are pulled across. So I guess we'll have to wait for ntopng to be updated as part of that
Does anyone know the ETA on this?
-
If we just missed the quarterly update (I have a feeling this was the case), it could be anything up to three months. jim-p would know.
-
If we just missed the quarterly update (I have a feeling this was the case), it could be anything up to three months. jim-p would know.
This is so unprofessional of PFSense that you brought up the issue in a bug report close to a pull date with sufficient action time, and Mr. Jim Pingle failed to act appropriately…the world changes a lot in three months...unacceptable.
-
I guess the team have to priotise somehow, as there's a lot of work in maintaining pfSense and all the packages. The new version is live now so you should be able to update in the packages manager in pfSense.
-
no the package manager still shows ntopng-3.0.2017.08.12
-
It's available on the development snapshots updates stream.
-
ah… Thanks!
-
Modifying a package repository doesn't seems would take more than a minute…as it's just updating an existing package link, unless the job also requires publishing a dissertation. I am still too new to figure out the development snapshots update stream...sure this applies to many other members as well.
-
just wondering if there is any way to upgrade this to the full non community version I need its full functionality for a school I work for
