Ntopng development
-
@Andrew453 Thanks for the details.
I see that 2.3.2 is not a stable build yet.
Guess I'll be waiting a little longer unless someone can correct you :)so I'm not aware of an easy way to install it on the current 2.3.1 release. (Happy to be corrected on that if someone can point me in the right direction).
-
… if you're happy to run off a development snapshot, you can specify the development branch in the update settings in pfSense, but that will update your entire system.
-
I've been following the developments very closely. There isn't any way ntopng is going to be included in 2.3.1 update 2, is there? Or will we need to wait until the stable release of 2.3.2?
-
If it proves stable enough on 2.3.2, it may be made available elsewhere. It's still being tested, though.
-
great. I think there's a lot of ppl waiting for it.
just because it's an excellent interface to monitor realtime bandwidth usage on the fw and I don't seem to be able to find a good alternative to it.
-
Thank you for adding this package! It is working well for me locally, but I am having issues with setting up ntopng over HTTPS via NGINX.
I have tried setting up a proxy_pass directive, but I cannot get past the login screen. I also tried editing the /usr/local/etc/rc.d/ntopng.sh file to add –http-prefix="/ntopng" to the startup strings, but unfortunately I get the same issue.
Can we integrate SSL certificates into ntopng or allow for native nginx https proxy through pfSense's nginx setup?
Thank you!
-
temporarily to fix the authentication/login issue through NGINX, I have added –disable-login '1' to the /usr/local/pkg/ntopng.inc file in the DNS Mode string:
/* DNS Mode */ if (is_numeric($ntopng_config['dns_mode']) && ($ntopng_config['dns_mode'] >= 0) && ($ntopng_config['dns_mode'] <= 3)) { $dns_mode = "--disable-login '1' --dns-mode " . escapeshellarg($ntopng_config['dns_mode']); }
I enabled htaccess password protection via nginx.
Everything is working great now! Thanks!
-
If it proves stable enough on 2.3.2, it may be made available elsewhere. It's still being tested, though.
Is there a chance that it will be included as an alpha release in 2.3.2?
-
It's already in 2.3.2. If you install a 2.3.2 snapshot you can use it now (or at least once I get this fix pushed to correct the password handling)
When 2.3.2 releases (probably next week) you'll have access to it.
-
any chance of pulling in the 2.4 version of ntopng that is available in FreeBSD ports?
The changelog is long, but the first 2 items alone seem enough to make it worth it:
-
Memory-management, stability and speed have been fundamentally improved
-
We have kept an eye on security and hardened the code to prevent privileges escalation and XSS
-
-
any chance of pulling in the 2.4 version of ntopng that is available in FreeBSD ports?
The changelog is long, but the first 2 items alone seem enough to make it worth it:
-
Memory-management, stability and speed have been fundamentally improved
-
We have kept an eye on security and hardened the code to prevent privileges escalation and XSS
After we release 2.3.2 we can look into that.
-
-
Great package, haven't used ntop in years and its great to get this level of detail back, thank you! Looking forward to ntopng 2.4
-
Hi Guys
Thanks to everyone involved in getting the ntopng package back into pfsense with version 2.3.2. Its great and works well.
Could I possibly ask for one, hopefully minor, improvement?
For the historical data could we specify the max period that the data is kept for eg. 30 days.
This is should be supported by ntop but I can't find the option to specify the limit before I enable the Historical Data storage
Ref: http://www.ntop.org/ntopng/exploring-historical-data-using-ntopng/Much appreciated.
-
The screen shown on that page is for a MySQL database. That isn't what is in use on pfSense. Eventually the package could grow the ability to export to an external MySQL server, but it wouldn't ever be using a MySQL database on the firewall itself.
-
How are people accessing the ntopng dashboard? I get an SSL error every I try to access it. I'm pretty sure it's because pfsense is using HSTS, and thus my browser always wants to connect via HTTPS instead of HTTP, but I'm not really sure how to work around this problem.
-
Use HTTPS for the GUI and ntopng
-
HTTPS for ntopng isn't working for me. I receive a SSL protocol error when attempting to access. I haven't tracked it down yet. HTTP via IP address works fine.
Use HTTPS for the GUI and ntopng
-
Wasn't too hard to find. HTTPS is disabled because there is no certificate installed. From ntopng.log:
27/Jul/2016 21:45:14 [HTTPserver.cpp:464] HTTPS Disabled: missing SSL certificate /usr/local/share/ntopng/httpdocs/ssl/ntopng-cert.pem 27/Jul/2016 21:45:14 [HTTPserver.cpp:466] Please read https://github.com/ntop/ntopng/blob/dev/doc/README.SSL if you want to enable SSL. 27/Jul/2016 21:45:14 [HTTPserver.cpp:509] Web server dirs [/usr/local/share/ntopng/httpdocs][/usr/local/share/ntopng/scripts] 27/Jul/2016 21:45:14 [HTTPserver.cpp:512] HTTP server listening on port 3000
-
Thanks Jimp
Using an external MySQL instance would be a great option.
For now though, if we enable the historical usage, where is it going to store the data?
If its in daily files I could just add a cronjob to wipe the older files after x days. Just a thoughtThe screen shown on that page is for a MySQL database. That isn't what is in use on pfSense. Eventually the package could grow the ability to export to an external MySQL server, but it wouldn't ever be using a MySQL database on the firewall itself.
-
Wasn't too hard to find. HTTPS is disabled because there is no certificate installed. From ntopng.log:
27/Jul/2016 21:45:14 [HTTPserver.cpp:464] HTTPS Disabled: missing SSL certificate /usr/local/share/ntopng/httpdocs/ssl/ntopng-cert.pem 27/Jul/2016 21:45:14 [HTTPserver.cpp:466] Please read https://github.com/ntop/ntopng/blob/dev/doc/README.SSL if you want to enable SSL. 27/Jul/2016 21:45:14 [HTTPserver.cpp:509] Web server dirs [/usr/local/share/ntopng/httpdocs][/usr/local/share/ntopng/scripts] 27/Jul/2016 21:45:14 [HTTPserver.cpp:512] HTTP server listening on port 3000
Have the same problem. Is there an easy fix (like symlink the real certificate)? Should/can this be fixed by the package maintainer?
-
I was getting my packages mixed up there. The ntopng package doesn't have an HTTPS option yet. It will need to be added to the package. I can look into it, but I have no idea when I'll be able to get around to adding that as a feature. If someone wants to make a pull request, have a look at the lightsquid package which has a cert selection for HTTPS that would be very similar.
-
Have they managed to get application filtering/control working in nTopng with pfsense?
That was what my original discussions with Luca Deri were about.
It's great to have nTopng working again from an analysis/reporting fashion, but the real power of the application is to be able to control applications instead of trying to do a half arsed job with Snort….
-
I don't think certificate selection code is necessary. The ntopng service is another port on the firewall itself. The certificate for ntopng would need to have the same common name and alternate names as the firewall itself. In other words, the certificate for ntopng is the same certificate used by the pfSense webgui.
I'll have a look at it when time permits.
-
Here you go:
https://github.com/pfsense/FreeBSD-ports/pull/172
Note that if you change between http and https for the webgui, either the ntopng settings will need to be re-saved or the system rebooted. Given how rare the switch is, I don't think this will be too much of an issue.
-
@Tram:
Thanks Jimp
Using an external MySQL instance would be a great option.
For now though, if we enable the historical usage, where is it going to store the data?
If its in daily files I could just add a cronjob to wipe the older files after x days. Just a thoughtThe screen shown on that page is for a MySQL database. That isn't what is in use on pfSense. Eventually the package could grow the ability to export to an external MySQL server, but it wouldn't ever be using a MySQL database on the firewall itself.
I haven't used ntopng in the last few months and looking over the doc, looks like sqlite support isn't there anymore for historical data. Looks like mysql or es flow-dumps are the only option now.
There is an error when 'Historical Data Storage' is enabled Im going to change the syntax to use the mySQL i have running
18/Aug/2016 08:49:31 [Prefs.cpp:792] WARNING: Discarding -F -i: value out of range
http://www.ntop.org/ntopng/exploring-historical-data-using-ntopng/
-
I was able to get mysql historical data to work.
I changed file /usr/local/pkg/ntopng.inc line 123 to something like this
/* Historical Data Storage, Dump expired flows */ if ($ntopng_config['dump_flows'] == "on") { $dump_flows = "-F 'mysql;mysql.server;ntopng;flows;ntopng;password'"; }
'mysql;mysql.server;ntopng;flows;ntopng;password'
mysql - letting it know you are using a mysql db
mysql.server - mysql server ip or hosename
ntopng - mysql DB name, you have to create a DB so i used ntopng for its name
flows - tablename prefix, it will create flowsv4 and flowsv6
ntopng - mysql username that needs write access to the db it will be inserting data into
password - password to the mysql user you are using to access you mysql serverI also swapped the syntax order on line 139. I put the interfaces before the historical data option
$start .= "\t/usr/local/bin/ntopng -d /var/db/ntopng -G /var/run/ntopng.pid -e {$disable_alerts} {$ifaces} {$dump_flows} {$dns_mode} {$aggregations} {$local_networks} &\n";
Only LAN is keeping historical data. Not sure why but my other interfaces are vlans so that may have something to do with it. Needs more testing to confirm.
I noticed the 'Local Networks' option hasn't been updated to grab IPv6 addresses from interfaces. I manually updated line 117 to include my IPv6 subnet and also some of the multicast subnets to keep them local instead of remote within ntopng
PS What happen to the preference menu item?
-
Version 0.8.4_1 with HTTPS support is rolling out now.
-
Version 0.8.4_1 with HTTPS support is rolling out now.
Is this package update version 2.4 of ntopng, or still the previous version?
-
It's the same version of ntopng, with the addition of support for HTTPS in the pfSense package.
-
I found bug with the ssl version. You may want to remove "\n" from the new code.
if ($config['system']['webgui']['protocol'] == "https") { $cert =& lookup_cert($config['system']['webgui']['ssl-certref']); ntopng_write_cert_file("/usr/local/share/ntopng/httpdocs/ssl/ntopng-cert.pem", $cert); $http_args = "-w 0 -W 3000\n"; } else { unlink_if_exists("/usr/local/share/ntopng/httpdocs/ssl/ntopng-cert.pem"); $http_args = "-w 3000\n"; }
It created the the startup file incorrectly
rc_start() { /usr/local/bin/redis-server --dir /var/db/ntopng/ --dbfilename ntopng.rdb & /usr/local/bin/ntopng -d /var/db/ntopng -G /var/run/ntopng.pid -s -e -w 0 -W 3000 -i 'em2' --dns-mode '0' --local-networks 'fe80::/10,192.168.0.0/24,2000:0000:0000:2400::/64' &
-
I found bug with the ssl version. You may want to remove "\n" from the new code.
You are quite correct. Not sure how I missed that in testing.
PR created.
Thanks
-
dennypage, is there some trick to getting someone to accept pull requests? I submitted one a couple weeks ago to add ipv6 addresses to "local-networks" in the ntopng command line, but it's gone idle as far as I can see…
(I'm just trying to figure out if I missed a step in the submission or not.)
Thanks
Gary -
dennypage, is there some trick to getting someone to accept pull requests? I submitted one a couple weeks ago to add ipv6 addresses to "local-networks" in the ntopng command line, but it's gone idle as far as I can see…
No special trick, but I went to look for your PR and couldn't find it. What is the PR number?
-
No special trick, but I went to look for your PR and couldn't find it. What is the PR number?
https://github.com/pfsense/pfsense-packages/pull/1262
-
I believe you want this repo here:
https://github.com/pfsense/FreeBSD-ports
which corresponds to packages in pfSense 2.3 and later.
Look in net/pfSense-pkg-ntopng.
-
I believe you want this repo here:
https://github.com/pfsense/FreeBSD-ports
which corresponds to packages in pfSense 2.3 and later.
Look in net/pfSense-pkg-ntopng.
Okay, thank you. I'll redo my patch tomorrow morning in that other repo.
-
I found bug with the ssl version. You may want to remove "\n" from the new code.
You are quite correct. Not sure how I missed that in testing.
PR created.
Thanks
Hello, I updated ntopng package to 0.8.4_2. From changelog it fixes problem with \n in startup script. BUT after upgrade still same config and startup file is generated. Edited it manually, removed newline but still not starting with error : "[HTTPserver.cpp:503] ERROR: Unable to start HTTP server (IPv4) on ports 3000s: Invalid argument". It only started after removing -W argument (HTTPS).
New bug or my problem?Modified ntopng.sh
rc_start() {
/usr/local/bin/redis-server –dir /var/db/ntopng/ --dbfilename ntopng.rdb &
/usr/local/bin/ntopng -d /var/db/ntopng -G /var/run/ntopng.pid -s -e -w 0 -W 3000 -i 'vmx1' -i 'vmx2' --dns-mode '0' --local-networks '192.168.0.0/16,172.16.0.0/12,10.0.0.0/8' &}
-
If you are using HTTPS enabled in the pfSense gui, you will need to visit the ntopng settings page (Diagnostics / ntopng Settings) and press save. This will cause the certificate to be set up in order to use HTTPS with ntopng.
-
It's the same version of ntopng, with the addition of support for HTTPS in the pfSense package.
Denny, do you know what the main reason is that the 2.4 version of ntopng isn't available in pfSense? I see the FreeBSD port has been ready for some time…
https://github.com/freebsd/freebsd-ports/blob/master/net/ntopng/Makefile -
I've just upgraded to ntopng 0.8.4_2 on pfSense 2.3.2 and get the following error message in the System Log:
ntopng [HTTPserver.cpp:503] ERROR: Unable to start HTTP server (IPv4) on ports 3000s: Invalid argument
The ntopng service is showing as stopped in the service status and the ntopng process isn't running (ie not appearing when I run ps aux or sockstat.
I've tried uninstalling, reinstalling, and unchecking the "Keep Data/Settings" options, but my settings seem to be kept, and the error remains. I've tried changing the settings in the GUI and re-saving as suggested a couple of posts up.
I do have a certificate (ntopng-cert.pem) in /usr/local/share/ntopng/httpdocs/ssl which gets regenerated each time I update the settings through the GUI.