New Traffic Totals package available for testing

jdillard

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)?

grandrivers

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

MikeV7896

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.

jdillard

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.

jdillard

@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.

jdillard

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>

Dazog

As requested:

grandrivers

MorpheusRO

jdillard

Thanks! I was finally able to replicate the blank interface issue, looking into it now.

athurdent

Will the vnstat database be included in the XML backup similar to RRD?

jdillard

In theory yes, but I haven't messed with that code yet.

jdillard

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'.

MyKroFt

still have a blank line - it used to show as my LAN interface

Myk

Capture.PNG_thumb

MikeV7896

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.

jdillard

I was able to reproduce on my home box. Hope to have a .5 out today.

MyKroFt

@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

Jabroni

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

MikeV7896

2.3.2 is likely going to be released this week, so it - and this package - will be available to the world soon enough.

jdillard

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.