`–# uname -a
FreeBSD Gate.domain 10.3-RELEASE-p17 FreeBSD 10.3-RELEASE-p17 #10 6da131e75c7(RELENG_2_3_3): Wed Mar  8 14:29:18 CST 2017    root@ce23-i386-builder:/builder/pfsense-233/tmp/obj/builder/pfsense-233/tmp/FreeBSD-src/sys/pfSense_wrap_vga  i386

Installing pfSense-pkg-ntopng...
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
The following 15 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
pfSense-pkg-ntopng: 0.8.6_1 [pfSense]
webfonts: 0.30_13 [pfSense]
mkfontscale: 1.1.2 [pfSense]
libfontenc: 1.1.3 [pfSense]
mkfontdir: 1.0.7 [pfSense]
fontconfig: 2.12.1,1 [pfSense]
ntopng: 2.4.2016.10.14 [pfSense]
ndpi: 1.8.2016.07.13 [pfSense]
GeoIP: 1.6.9 [pfSense]
luajit: 2.0.4_1 [pfSense]
mysql56-client: 5.6.35_1 [pfSense]
liblz4: 131 [pfSense]
graphviz: 2.38.0_14 [pfSense]
redis: 3.2.6 [pfSense]
gdbm: 1.12 [pfSense]

Number of packages to be installed: 15

The process will require 119 MiB more space.
9 MiB to be downloaded.
[1/15] Fetching pfSense-pkg-ntopng-0.8.6_1.txz: .. done
pkg: pfSense-pkg-ntopng-0.8.6_1 failed checksum from repository
Failed

I have the same issue as drinny… March showed up as February... April is showing up as April. It was a clean install in the middle of March, so I don't have the actual month of February to compare to.

I just wanted to follow up on this problem. I have been working a little more on it. When I Uncheck the "Keep Data/Settings" box and uninstall it seems to keep my settings, the only working interfaces I have seemed to gotten back are my wan connection and my wireless card. The ethernet connection still will not show up under interfaces n the ntopng gui menu.

I would really like to get that interface working again since it is my main network. The wireless is not important because it is more of a failsafe.

Thank you dennypage. I'll give myself a break for a few days then I'll dive back to traffic shaping abyss (this will also help with my popularity. I've seen people outside the office protesting with signs "We are not lab mice – No more experiments with the internet during working hours").

I have been using pfsense on 2.3.2-RELEASE (amd64) my problem is ntopng it worked until my router is reboted after lost light . Now ntopng doesn't start without redis-server . For starting service i have to activated it with config ,  i mean redis-server /usr/local/etc/redis.conf then i start ntopng .
If you want to see my logs :

ntopng : 27/Mar/2017 17:34:15 [Prefs.cpp:919] Logging into /var/tmp/ntopng/ntopng.log
27/Mar/2017 17:34:15 [Ntop.cpp:1121] Setting local networks to 127.0.0.0/8
27/Mar/2017 17:34:17 [Redis.cpp:79] ERROR: ntopng requires redis server to be up and running
27/Mar/2017 17:34:17 [Redis.cpp:80] ERROR: Please start it and try again or use -r
27/Mar/2017 17:34:17 [Redis.cpp:81] ERROR: to specify a redis server other than the default

syslog : Mar 27 11:02:48 pfSense php-fpm[280]: /rc.start_packages: [ntopng] Cannot set admin password - redis-server is not running.
Mar 27 11:02:50 pfSense ntopng: [Redis.cpp:79] ERROR: ntopng requires redis server to be up and running
Mar 27 11:02:50 pfSense ntopng: [Redis.cpp:81] ERROR: to specify a redis server other than the default
Mar 27 11:03:10 pfSense ntopng: [Redis.cpp:79] ERROR: ntopng requires redis server to be up and running
Mar 27 11:03:10 pfSense ntopng: [Redis.cpp:81] ERROR: to specify a redis server other than the default
Mar 27 11:06:42 pfSense ntopng: [Redis.cpp:79] ERROR: ntopng requires redis server to be up and running
Mar 27 11:06:42 pfSense ntopng: [Redis.cpp:81] ERROR: to specify a redis server other than the default
Mar 27 11:12:30 pfSense ntopng: [Redis.cpp:79] ERROR: ntopng requires redis server to be up and running
Mar 27 11:12:30 pfSense ntopng: [Redis.cpp:81] ERROR: to specify a redis server other than the default
Mar 27 11:14:24 pfSense admin: /usr/local/etc/rc.d/redis: WARNING: failed to start redis
Mar 27 11:18:52 pfSense ntopng: [Redis.cpp:79] ERROR: ntopng requires redis server to be up and running
Mar 27 11:18:52 pfSense ntopng: [Redis.cpp:81] ERROR: to specify a redis server other than the default
Mar 27 11:20:33 pfSense ntopng: [Redis.cpp:79] ERROR: ntopng requires redis server to be up and running
Mar 27 11:20:33 pfSense ntopng: [Redis.cpp:81] ERROR: to specify a redis server other than the default
Mar 27 11:20:48 pfSense admin: /usr/local/etc/rc.d/redis: WARNING: failed to start redis
Mar 27 12:22:30 pfSense ntopng: [Redis.cpp:79] ERROR: ntopng requires redis server to be up and running
Mar 27 12:22:30 pfSense ntopng: [Redis.cpp:81] ERROR: to specify a redis server other than the default
Mar 27 12:24:27 pfSense ntopng: [Redis.cpp:79] ERROR: ntopng requires redis server to be up and running
Mar 27 12:24:27 pfSense ntopng: [Redis.cpp:81] ERROR: to specify a redis server other than the default
Mar 27 12:24:47 pfSense ntopng: [Redis.cpp:79] ERROR: ntopng requires redis server to be up and running
Mar 27 12:24:47 pfSense ntopng: [Redis.cpp:81] ERROR: to specify a redis server other than the default

Redis logs : /var/log/redis/redis.log
13771:M 27 Mar 16:06:34.087 * 10 changes in 300 seconds. Saving…
13771:M 27 Mar 16:06:34.087 * Background saving started by pid 73803
73803:C 27 Mar 16:06:34.092 * DB saved on disk
13771:M 27 Mar 16:06:34.194 * Background saving terminated with success
13771:M 27 Mar 16:11:35.077 * 10 changes in 300 seconds. Saving...
13771:M 27 Mar 16:11:35.078 * Background saving started by pid 89520
89520:C 27 Mar 16:11:35.083 * DB saved on disk
13771:M 27 Mar 16:11:35.181 * Background saving terminated with success
13771:M 27 Mar 16:16:36.083 * 10 changes in 300 seconds. Saving...
13771:M 27 Mar 16:16:36.083 * Background saving started by pid 11670
11670:C 27 Mar 16:16:36.088 * DB saved on disk
13771:M 27 Mar 16:16:36.190 * Background saving terminated with success
13771:M 27 Mar 16:21:37.029 * 10 changes in 300 seconds. Saving...
13771:M 27 Mar 16:21:37.030 * Background saving started by pid 32620
32620:C 27 Mar 16:21:37.035 * DB saved on disk
13771:M 27 Mar 16:21:37.137 * Background saving terminated with success
13771:M 27 Mar 16:26:38.083 * 10 changes in 300 seconds. Saving...
13771:M 27 Mar 16:26:38.084 * Background saving started by pid 81885
81885:C 27 Mar 16:26:38.089 * DB saved on disk
13771:M 27 Mar 16:26:38.191 * Background saving terminated with success
13771:M 27 Mar 16:31:39.071 * 10 changes in 300 seconds. Saving...
13771:M 27 Mar 16:31:39.072 * Background saving started by pid 24264
24264:C 27 Mar 16:31:39.077 * DB saved on disk
13771:M 27 Mar 16:31:39.173 * Background saving terminated with success
13771:signal-handler (1490632348) Received SIGTERM scheduling shutdown...
13771:M 27 Mar 16:32:28.955 # User requested shutdown...
13771:M 27 Mar 16:32:28.955 * Saving the final RDB snapshot before exiting.
13771:M 27 Mar 16:32:28.968 * DB saved on disk
13771:M 27 Mar 16:32:28.968 * Removing the pid file.
13771:M 27 Mar 16:32:28.968 # Redis is now ready to exit, bye bye...

While it is a great device, the SG-1000 does not have sufficient RAM/CPU to run a giant application like ntopng.

well that might be true, but seemed to see what was the issue, i had to uncheck the historical data that was causing the kernel panic

delete the ntop files using FTP filezilla then install again the ntop

There does seem to be an issue with ntopng not always restarting cleanly.  Restarting the ntopng service usually works for me, though sometimes it takes a couple of goes until it gets it right.

I've been doing this a lot recently - trying to make up for ntop not reporting in predictable periods.  It works for me, but sometimes I have to restart ntopng more than once.  My process is:

* ntopng settings
        - take the tick out and save.
        - click delete data
        - put the tick in and save

After the many seconds of delay after that last save I try to access ntopng.  Sometimes it works straight away and sometimes it doesn't (times-out).

If it doesn't work, I use the pfsense services list to stop and then start ntopng.  Usually ntopng will work again at this point, but sometimes I have had to try a second or a third time before it all works again.

Obviously not ideal, but that's what I've been doing for now.

None of this would be necessary if ntopng would allow reporting in fixed periods.

this is a great package.  took a little bit to get used to!  Thanks

xawen, yes it sounds like we are both looking for the same thing.

As noted in my thread, the only (temporary) solution I have found is to read the ntop data at midnight and then clear its logs so I can read it the next day.  I've been doing this manually at the moment, just to try and get a hint at what's going on, and to get some base figures.  Obviously a manual approach is no good for anything more than a few days.

I'm pretty certain ntop already has everything needed to give us what we want EXCEPT the user interface support to show it.  It's quite frustrating.  I know it is "cute" to see current flows, but I can't figure how why there don't seem to be more people interested in historical views of this data: except in times of crisis, current flows are pretty useless, trends (using comparable periods of data) are much more interesting (or so it seems to me).

ntop definitely has the data, what it lacks is the user interface to present it the way I need it.  It is possible the paid version might have something, but I can find nothing in the user manual (which includes paid version details).

Of course, since it is open source I guess I could try to add what I need … but not sure if I have the necessary skills, and I definitely don't have the time at the moment.  The only other alternative would appear to be to export its totals and collate them in some other package.

I discovered another complication.  It looks like lightSquid's "day" is (if you update every hour) is actually 23:00..22:59 (the update they run at midnight goes into the next day (despite the fact that it is obviously counting traffic from the previous day).  So it just gets harder and harder to compare figures.  (My network is small enough I could probably run lightsquid's update more often and reduce the problem.)

Deleting ntopng data just before midnight (disable the service, hit the delete data button, restart the service, then restart it again before it will actually work) clears most of its history (but not traffic totals).  And using this I've been able to see that ntop's totals come close enough to the "Traffic Totals" package, both of which are close to the ISP totals for the day.

Without having collected the history going back to December or early January I cannot see for certain what has blown out in my network use, but since ntop's "Facebook" application is something like 40% to the total I am guessing it must be a significant part of it (none of the other totals are large enough to hide the approx 300MB a day that the traffic has increased - up from around 700MB/day to 1000MB/day).

So ntopng has helped (or offers hints), it's just a shame it doesn't offer consistent, comparable historical analysis from its current user interface.

I hope so!  (Not a very useful response but this is what I have just started using it for - since it is specifically WAN traffic I am trying to identify.)

It does include some alert items that suggest it is intended for the WAN interface (eg: Suspicious Activity: "Probing or Server Down" messages).

As for how it is capturing this information, you are probably best advised to look at the ntop website http://www.ntop.org/products/traffic-analysis/ntop/  they speak about being based on libpcap and collecting flows through nprobe.

Yeah I guess better wait and check it again when the ntopng package is updated to a newer snapshot build.

ntopng github had a bunch of commits recently for FreeBSD in the dev branch, worth taking a look

https://github.com/ntop/ntopng/commits/dev