PfSense 2.3 new Traffic Graph doesn't include total Traffic in time period
-
Hi,
Just curious if there has been any progress made on it. The gif looks perfect!
Thanks,
RichI second this!!
-
Not quite as nice as having all those graphs presentable as they were with RRD, but a damned sight better than what is here now.
Heck if RRD is still even possible I'd prefer that as a downloadable package, unless this new tool can 1-up the old tools. RRD wasn't always very accurate, especially with older data. But at least is was something I could pull up and argue with the ISP when they pull some of the crazy stunts they do.
-
Hi,
Just curious if there has been any progress made on it. The gif looks perfect!
Thanks,
RichIt's closer: https://forum.pfsense.org/index.php?topic=109700.msg634458#msg634458
-
Has anyone else noticed that the "Last Month" traffic numbers under RRD Summary are an order of magnitude higher?
I looked at my current month total yesterday (6/30) and it was ~ 1,200,000 MB
Today (7/1) my last month total is ~ 13,028,404 MB! -
Is there a way to get any traffic stats beyond current at the moment stats?
I am looking to cut the cord with my cable company & am looking to stream a number of devices but want to make sure I can do it. Just curious if we have any other update or another suggestion on how to check traffic.
-
Can we also add to save the current selections on the monitoring page?
It is painful to return to the page and have to re-select all your options again.
-
Take a look over at the 2.3.2 forum, some good new stuff:https://forum.pfsense.org/index.php?topic=114753.msg637619#msg637619
-
Can we also add to save the current selections on the monitoring page?
It is painful to return to the page and have to re-select all your options again.
There is a 'Save as Defaults' under the Advanced section.
-
Hello, all.
I'm just curious if the addition of 'RRD_Summary' and 'Status_Traffic_Totals' packages essentially closes this topic or is there a plan to bring this functionality back to native pfSense?
Thanks,
Brian -
At least it worked.
-
@cmb:
Because it's a function of rrdtool graph, which has absurdly large dependencies in latest rrdtool. jdillard's working on a replacement with vnstat.
It worked.
-
+1 !!
Please bring it back!! -
The data it displays is not even close to correct now, its not just total inpass is no longer a sum of all data for the period
ntopng and rrd on the same system are way off, ntopng has some issue where you must select traffic even though its the default otherwise the min and max pull reported are averaged but ntopng is correct
rrd still needs to be fixed, it was very useful in proving packet loss and latency issues to ISPs, countless times we have been able to get ISP to escalate tickets when they were telling us "no issue"
ntop is over the head of most of the ISP support people on packet loss and it does not do latency at all (ntopng lacks nprobe)
in case of Time Warner, their high up techs have access to rrd tools monitoring the modem, and the rrd reporting use to match, now it does not
-
I don't believe this.
The one reason I switched to pfsense was cause it didn't loose total traffic on reboot compared to my plastic router, and now don't even show it ?
Just when Comcast roll it's 1TB data cap for home users and now somebody decide it's not no longer relevant feature to have, really ? After so much advanced features pfsense has, it can't even show you if you are over you data cap ? I am very disappointed, I even support the pf-sense project for future development.
If we are willing to revert to much older version of pf-sense just to get this crucial functionality back(disregarding any other changes for the last year as not as important as this), how come this is happening.
P.S. This is so bad. I can only speculate why , but I guess in something internally changed significant in pf-sense team, perhaps the whole thing switched hands. I had my 2.2.6 running for a year, and finally decide to upgrade. What a shame. I am glad I didn't donate as I was intending to, but upgrade first.
-
THe RRD_Summary package shows this and last months WAN traffic in the time period and is accurate enough to check how near a usage cap I am. Good enough for me although not exactly the presentation of data which used to be available. Many ISP's will send an E-mail when usage is near the cap.
J
-
This is so bad. I can only speculate why.
You were told exactly why:
"we cut the graphing utility out because it was going to double the total size of the pfSense image."
Double. Just for that one function.
-
THe RRD_Summary package shows this and last months WAN traffic in the time period and is accurate enough to check how near a usage cap I am. Good enough for me although not exactly the presentation of data which used to be available. Many ISP's will send an E-mail when usage is near the cap.
J
Thanks for the suggestion. I already install the package. It does the job till some future update made the package obsolete , but it works for now. Thanks
As far is "Many ISP's will send an E-mail when usage is near the cap." in this case you rather get their router and be done with it, but I don't think pf-sense is about that type of users.
-
This is so bad. I can only speculate why.
You were told exactly why:
"we cut the graphing utility out because it was going to double the total size of the pfSense image."
Double. Just for that one function.
The question is : Do you really believe that ?!?
Functionality to create graphs out the data is already there. We are talking about the functionally to count the data passing through the WAN interface. Is that what is going to double the size of the image ? I don't think one need to be familiar with coding to guess how much code it will take to do that.
-
perhaps you should just install the "Status_Traffic_Totals' package ?
-
perhaps you should just install the "Status_Traffic_Totals' package ?
Thanks for the suggestion.I did that and I'll have to admit is looking and working great.
My only worry is this: Since it's a package now, next few updates of the pfsense itself may broke it's functionality and all the accumulated data going back to the drain.
