New Traffic Totals package available for testing
-
@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.
