New Traffic Totals package available for testing
-
Are you using the ram disk? then you could try this on: https://forum.pfsense.org/index.php?topic=114753.msg664804#msg664804
Under "Status" / "Traffic Totals" click on "Display Advanced" -> "Enable Graphing" and "Save as Default"
-
why not just use the drive pfsense is installed on? my pfsense is installed on a 60 gig ssd, plenty of space for storing this sort of data :)
-
Known issues:
#1) There is an issue with the stacked bar graph. Documented here: https://github.com/novus/nvd3/issues/341#issuecomment-222370991
I believe I may have found another bug that only occurs with the stacked bar graph. I have been collecting data for a couple of days now and all totals look fine except with stacked bars (see image): for some reason the (rx) values are displayed as KiB instead of GiB and the resulting higher values seem to hit a type related cap and show up as negatives .
This is from a pfSense 2.3.2 (latest) on an ALIX APU.1D4.
Edit: This only occurs with inverse mode on. Btw. would it be possible to save defaults for Hourly and Daily etc. separately?
-
I observed on my pfSense box that openvpn traffic is been reported the same as WAN traffic. To me this isnt a big deal as I only care about monitoring my WAN usage, but I am reporting here. It is not exactly the same as in 1:1 but is very close to the WAN figures.
The only actual traffic on my openvpn (since I still am only testing it on pfSense) is an idle ssh session to one server.
-
A word of warning, this package and its data is not backed up when using the pfsense backup wizard, I have just migrated to zfs, and pretty much everything is intact except this plugin was missing and I have had to set it up again.
-
Read this and same here.
Did it yesterday, this is the only thing missing. -
It suddenly stopped working, I get this error: Error: {"vnstatversion":"1.14","jsonversion":"1","interfaces":[Error: Database load failed even when using backup (No such file or directory). Aborting.
What to do? I haven't changed anything. -
@chrcoluk:
There's no export function for this package yet, you have to manually backup the databases.
vnStat has an export function that could be used to dump the databases to config.xml similar to RRD. But it would need some logic to convert the hardware interface names to the pfSense naming scheme and back. The databases contain something like i.E. igb1 instead of OPT2.@BabaBooey:
What's the content of/var/db/vnstat on your system?@jdillard:
Any chance for a backup function? It would also be nice to use the vnStat daemon instead of a cron job. We lose up to 5 minutes interface data when rebooting, don't we? -
.igb0 .igb1 .igb2 .igb3 .igb4 .igb5 igb0 igb1 igb2 igb3 igb4 igb5
-
.igb0 .igb1 .igb2 .igb3 .igb4 .igb5 igb0 igb1 igb2 igb3 igb4 igb5
Seems your vnStat databases became corrupted then, could be because of a system crash and reboot. Or you HDD could be dying.
-
I had a couple of unexpected power failures earlier this winter, due to a space heater, could that be it?
My pfsense box(Netgate SG-4860) seems to be working just fine, so the hardware should be fine, I hope so anyway :)
Is there a way to empty the db and start anew? If so, how do I do that? -
I think the switch Reset Graphing Data should work. If not you can always delete all the files in the vnstat directory to start over.
Power failures are a good reason for databases to get corrupted, yes.
-
Thank you I really appreciate your help :D
-
Is there a way to have the traffic graph data enabled between power reboots?
-
-
Is there a way to have the traffic graph data enabled between power reboots?
??? ??? ???
In the Total Traffic Stats package, on a reboot, the graphing isn't enabled. I have to re-enable it.
Even after 'save as defaults' is selected. -
Maybe try the "Save as defaults" button
-
-
Hi,
I got also the bug where the cron job disappear. Also only the option "Disable Graphing" appear but no more the "enable" option. Tries to remove and reinstall with the same result. The issue come after the bug where the databases of the vnstat tool were corrupted.
But what a great tool! :)
Thanks! -
After every single reboot, this is displayed.
No matter what I have tried. I have removed and re-installed the package.