New Traffic Totals package available for testing
-
It uses a cron job not vnstatd, I thought it would be more reliable.
Why is the vnstatd daemon unreliable on FreeBSD? Had it running for years on a Linux box with no problems at all.
He didn't say that it was unreliable on FreeBSD… just that he thought it would be more reliable as a cron job. Using the cron job, it's only running every 5 minutes rather than a constantly running process that could be stopped at any time leaving holes in the data.
I see pluses and minuses to both ways... I personally have no preference. I just want it to work and accurately track my usage. It doesn't need to be minute-by-minute... updating every 5 minutes is fine by me. Most of what I care about (and probably most people) is monthly usage more than anything.
-
Hmmm…
Is this topic about the new graphing system on 2.3 which replaced RRD? Or is it an addition to that? Or is it just a similar graphing to what's already built-in?
Why as a separate package? -
@virgiliomi:
He didn't say that it was unreliable on FreeBSD… just that he thought it would be more reliable as a cron job. Using the cron job, it's only running every 5 minutes rather than a constantly running process that could be stopped at any time leaving holes in the data.
Cron jobs are run by a daemon that could also be stopped at any time ;) So the question remains, why not use the vnstat daemon? Don't get me wrong, I just want to understand it, don't want to offend anyone :)
-
@virgiliomi:
Just wondering about why PHP is listed as a dependency for the package. Isn't PHP part of the whole pfSense ecosystem anyway? Or is that for future planning if it goes away? Does this potentially cause problems if PHP is upgraded by pfSense core, but the package isn't updated to reflect the new version of PHP, when someone goes to install the package?
I had a line in the Makefile that didn't need to be there. I'll be taking it out and it should remove the PHP dependancy.
-
It uses a cron job not vnstatd, I thought it would be more reliable.
Why is the vnstatd daemon unreliable on FreeBSD? Had it running for years on a Linux box with no problems at all.
It's not unreliable on FreeBSD, just harder to tie into all the necessary GUI bits last time I looked. Maybe I was looking at it wrong.
-
Hmmm…
Is this topic about the new graphing system on 2.3 which replaced RRD? Or is it an addition to that? Or is it just a similar graphing to what's already built-in?
Why as a separate package?TL;DR: RRDTool graphing dependancies got too large so we cut them out. Part of that was the function that provided the period totals. Period totals using RRD data aren't that accurate to begin with since they get averaged out over time. vnStat handles the collection of historical traffic totals better and is more accurate, hence the addition. Also, not everyone cares about traffic totals so no need to bundle it in core and having it as a package allows it to be revved separate from core.
-
Period totals using RRD data aren't that accurate to begin with since they get averaged out over time. vnStat handles the collection of historical traffic totals better and is more accurate, hence the addition. Also, not everyone cares about traffic totals so no need to bundle it in core and having it as a package allows it to be revved separate from core.
In that case, replacing Period totals with vnStat in the future would make many people happy.
-
under interfaces 2 of my 4 interfaces dont show but if i click the blank area datas there
-
I don't see anything in the interface selection.
I can click through the blank space and it does follow
I'm using VLANS on a single LAGG of two physical interfaces.
The totals do show up for my physical and ovpn interfaces, but none of those are assigned labels. -
Ok I'll have to look into the code that generates the interface names, I have a feeling it is making the option element, but not populating it with content. Grandrivers, do you happen to know what makes those 2 interfaces that aren't showing up different from the others (based on type, etc)?
-
one is a pppoe WAN the other is a non assigned opt interface but had not noticed the neither of my HE ipv6 tunnels show up at all might be nice to have those as well
-
I wonder if there's limits to what vnstat can track usage for… because interfaces that seem to be showing up are physical interfaces, while non-physical ones - VLANs, tunnels, etc. - don't seem to be showing up.
Also, the interfaces selected show their pfSense names (WAN, LAN, GUEST), but in the graph and table they're identified as the actual physical interface (igb0, igb1, igb2). I also have a blank entry, which is my unassigned igb3 interface. This is part of what leads me to the above suggestion that vnstat may only be able to track physical interfaces.
-
Just bumped the version to 0.2. It should include misc fixes as well as fixes for:
#6) The correct units and axis label. Although, I have to figure out how to make a custom axis format as it uses binary prefixes and not the SI prefixes.
#7) PHP shouldn't be listed as a dependency anymore. This may take some more kicking to get to work.
#8) Don't allow TOP 10 when multiple interfaces are selected.
-
@virgiliomi:
I wonder if there's limits to what vnstat can track usage for… because interfaces that seem to be showing up are physical interfaces, while non-physical ones - VLANs, tunnels, etc. - don't seem to be showing up.
Also, the interfaces selected show their pfSense names (WAN, LAN, GUEST), but in the graph and table they're identified as the actual physical interface (igb0, igb1, igb2). I also have a blank entry, which is my unassigned igb3 interface. This is part of what leads me to the above suggestion that vnstat may only be able to track physical interfaces.
It could also have to do with the get_interface_list() function I am using. I might need to use a different function or a combination of them, I am in the process of testing get_configured_interface_with_descr().
Edit: Bad news bears, this is what the vnStat man page says:
Virtual and aliased interfaces cannot be monitored because the kernel doesn't provide traffic information for that type of interfaces. Such interfaces are usually named eth0:0, eth0:1, eth0:2 etc. where eth0 is the actual interface being aliased.
-
For those that have blank interface issues can you view the page source (or inspect the element if you know how) and grab the HTML for the select element with id="interfaces".
It should look something like:
<select class="form-control" id="interfaces" name="interfaces" multiple=""><option value="em0" selected="">wan</option></select>
-
As requested:
<select class="form-control" id="interfaces" name="interfaces" multiple=""><option value="igb3" selected="">lan</option></select>
-
<select class="form-control" id="interfaces" name="interfaces" multiple=""><option value="igb1" selected="">opt1</option><option value="igb2" selected="">lan</option></select>
-
<select class="form-control" id="interfaces" name="interfaces" multiple=""><option value="igb0" selected="">wan</option><option value="igb1" selected="">opt3</option></select>
-
Thanks! I was finally able to replicate the blank interface issue, looking into it now.
-
Will the vnstat database be included in the XML backup similar to RRD?
-
In theory yes, but I haven't messed with that code yet.
-
I just pushed version 0.4 and it should fix:
#6) Units are more accurate and consistent. it was mostly fixed before, but there were a couple small errors.
#10a) Interfaces shouldn't show up blank anymore, but it is recommended to reset the graphing data after updating the package.
#10b) not really a fix, but it doesn't look as bad as previously thought. I can pull in VLANs, IPSec, and PPPOE. More interface types will need to be tested. If you want to see which interfaces vnStat can capture data for you can run the command 'vnstat –iflist'.
-
still have a blank line - it used to show as my LAN interface
Myk
-
I don't think that the update was released last night yet… I had updated my pfSense build maybe 15-20 minutes before your post time and the package manager still showed the .3 version of this package.
-
I was able to reproduce on my home box. Hope to have a .5 out today.
-
@virgiliomi:
I don't think that the update was released last night yet… I had updated my pfSense build maybe 15-20 minutes before your post time and the package manager still showed the .3 version of this package.
I had the latest update released .4
Myk
-
This is what just what i missed since the 2.2, but now finally Im going to be able to see how am i doing with the daily/weekly/monthly traffic per interface
Will this be run as a stand alone package we can install on a stable train?? Or we need to upgrade to the snapshots in order to get it install/show ?
Tried looking as a package on a 2.3_5 but it didnt show
-
2.3.2 is likely going to be released this week, so it - and this package - will be available to the world soon enough.
-
I just pushed changes for version 0.5, which should fix:
#10a) hopefully this one fixes the blank interface names
#4) can store defaults now!
#3) It can pull the start day from the new config options, but if you changed start day to any day except for "1" you will need to re-save that day again for it to show correctly.
-
Can I split information per user in LAN network?
I would check how much data download from Internet each user on LAN.
-
No, per user stats is not the purpose of this package.
-
Can I split information per user in LAN network?
I would check how much data download from Internet each user on LAN.
You'll probably want to look at ntop or darkstat… a note that darkstat's data resets when pfSense reboots. ntop is persistent, but over time can become a rather large amount of data.
-
Latest snapshots with Traffic Totals 0.5 is out now.
-
moved - sorry jdillard!
-
Please keep discussions on topic and make a new thread for topics not about this package.
edit: Thanks luckman212, and no worries.
-
Latest snapshots with Traffic Totals 0.5 is out now.
where do we look to find this? I am on 2.3.2.a.20160717.2316 and I still see only 0.4_1 … does it take time to roll out to a mirror site or something?
-
Can the save defaults also save which graph of the 4 for default as well?
also can the left side numbers be shortened MB,GB,TB etc?Thanks for your work on bringing this plugin back from the dead!
Myk
-
Latest snapshots with Traffic Totals 0.5 is out now.
where do we look to find this? I am on 2.3.2.a.20160717.2316 and I still see only 0.4_1 … does it take time to roll out to a mirror site or something?
Maybe try upgrading pfSense to the latest snapshot. I already had it installed on 2.3.2.a.20160715.0559 and was able to upgrade to 0.5. Sometimes if work is done to the package system it can mess with package upgrades showing up.
-
Can the save defaults also save which graph of the 4 for default as well?
Oops forgot to test that part, I'll get that in 0.6.
also can the left side numbers be shortened MB,GB,TB etc?
That is #6b on the TODO list. I have to figure out how to make a custom format for the axis ticks since it uses 1024, instead of 1000 for SI units.
-
Maybe try upgrading pfSense to the latest snapshot. I already had it installed on 2.3.2.a.20160715.0559 and was able to upgrade to 0.5. Sometimes if work is done to the package system it can mess with package upgrades showing up.
Oh I think I know why, because I'm on factory, not CE. Maybe those take a little longer to show up. I see CE 20160718-1342 is out but I don't want to switch to the CE track. Did that once before and I wound up having to pave the box to get back on factory.