I installed this last week and it's working well for the daily and monthly traffic totals. The hourly graph though is misbehaving. Instead of showing the last month, it is labeled as being from about yesterday through January 21st, 2021 or so. I don't know if it's just an issue with the rendering itself or if the underlying data is corrupt. Are others seeing this behavior? Screen Shot 2020-12-21 at 9.20.55 AM.png

Hi Gertjan,

I was wondering if you have receive any update regarding thei ssue.

Regards,
Ivan

@beachbum2021 no... look at the cpu usage in the web interface while you are running the speedtest. If it's pegged then maybe the small pucks are weaker than i thought. I usually build my own boxes....it's quite a bit cheaper for more powerful hardware. I used the sg at some locations that do not have gigabit connections.

also try going to a machine behind the firewall and running speedtests from a web browser. Also monitor the cpu usage during the tests. Might have hit the limit of the unit....

@bingo600 Are people being, generally, smart? Understanding that it's not obedience but a sense of collective self preservation.

Something that has been absent here in the US. :(

Anyhow, be well! I have noted those projects you shared for future messing around. :)

@cburbs I was able to install ntopng 4.2 from www.freshports.org/net/ntopng using ntopng-4.2.d20201102,1.txz in the 'pkg add' statements above.

@pfsense99 it's data rate bits per second and it's linear.

issue created: https://redmine.pfsense.org/issues/11069

This might be related to the issue I just discovered.

It looks like traffic totals no longer caps off the max entries.

So e.g. hourly should only show last 24 hours, Daily last 28/29/30/31 days and so on.

On my local unit If I wait long enough the hourly shows up and its got over 40k hours of data on it.

To see if it is just a local unit problem (corrupt database etc.) I checked another pfsense install and it is also above 24 hours. So looks like this package might be broken on new builds of pfsense, as it used to work properly originally.

In addition my local unit has many hours as 0 bytes of data, it is consistently <value> 8 hours of 0 bytes <value> 8 hours of 0 bytes <value> and so on.

--update--

Actually my issue might have been different.

I noticed I had device files in the vnstat database dir for devices that shouldnt be tallied, I disabled graphing, deleted the files, turned it back on, and now it is cutting off excess entries again, although I have lost all hourly and daily data (I assume due to them been corrupt), monthly data is instact so not end of the world,

The other unit has no device files at all in the directory, just the main database, so not sure what is going on with that one.

@gwaitsi no one knows how to limit the space used, or to clear data automatically after some period, etc? Alternatively, i am use the RAM for /var & /tmp option. is it possible to change the directory used, so it doesn't use ram?

I would like to re-enable if possible

Good news, it was a jQuery issue [.load() removed in favor of .on( "load", handler )]: https://redmine.pfsense.org/issues/10911#change-48604
The package has been updated.

As far as just a basic traffic monitor for interfaces on pfSense? This is probably the best. Others do a lot more, like tracking individual hosts/devices, what they're connecting to, etc. and might not track the interface as a whole.

To be honest, as long as you know the time difference, it's still doing what it should be doing. Plus, while my hourly graph seems to be horribly screwed up (it's showing that the current hour is 10/22/2020 11:00 AM), the daily and monthly graphs seem to be fine. And it's that monthly graph that you'd be most concerned about when checking against a data cap.