I checked on an old 2.3 build (prior to the new graphs) and the traffic graph looked like this then as well. I'll look into it some more, but so far haven't found a fix.

Its difficult to fix these issues as pfBlockerNG is a package and not tightly woven to pfSense… When pfSense is rebooted or if the box loses power, the package doesn't see the event and has no way to remove this line from the Unbound Adv settings:

server:include: /var/unbound/pfb_dnsbl.conf

So your best bet, is to remove that line and save the Resolver settings. Then reboot. If it reboots and the file pfb_dnsbl.conf is missing, unbound will not start and cause other issues.

there is a redmine related to ramdisk so no idea if the above would solve that, installing the pfsense-base package solved the GUI not showing updates for me.
u can run the above commands again and see if it solves for u, it wont harm the system but if something is broken it might fix it

Confirming _4 package works as well.

https://github.com/pfsense/pfsense/pull/2708

Not the first time this has been brought up.  Probably not the last either.

Just have to understand the perspective from which the values are being represented.

The development board here is a good place to start, eventually a feature request ticket may be made in redmine set to "future" once the details have been worked out.

resolved this, more info on below link
https://forum.pfsense.org/index.php?topic=107665.msg600840#msg600840

only the build nubmer not incrementing, squid general page save issue still persists

Oh, I see what you mean. I thought at first look that was a different, unrelated connection. Yeah I'll fix that.

i just tried to gitsync but its trying to install git which fails

update

after fiddling a little more managed to install git and did a gitsync master so the RRD stuff is now gone for good and new monitoring started showing up, but the strange thing is the pfsense build date still shows the day i upgraded and not the the build date of the current snap which i updated to which is the latest 5th march snap using option 13 in console

UPDATE

resolved this using the below link
https://forum.pfsense.org/index.php?topic=107665.msg600840#msg600840

@jdillard:

@athurdent:

Looks great!
But please bring back the total traffic count that was previously labeled "period". It is very useful to see how much traffic was generated…
Or is that already in and I just do not get how to use the new system? :)

This isn't as straightforward as it seems, I'll try and get it back in, but as you can see there can be accuracy issues: https://forum.pfsense.org/index.php?topic=107731.0

Have you been able to find a way to get it back in? If not, maybe add some kind of Vintage button as a link to the old RRD system?

Yeah it makes sense :)

Works like a charm.

Thanks!

:-[ yes, a refresh solved the "Problem"

The pool overlap issue is fixed for me, thanks a ton cmb!

my new dhcp pool:  ::b00b:0 - ::b00b:f331

yea the data is there, the code just isn't picking up the data. It will be fixed later today.

I have got the same problems. Also started after enabling ramdisks. Disabling them does not help.

results from pkg info 'pfSense-* are:
pfSense-pkg-Service_Watchdog-1.8.2_1
pfSense-pkg-openvpn-client-export-1.3.6_1
pfSense-pkg-pfBlockerNG-2.0.7
pfSense-pkg-snort-3.2.9.1_6
pfSense-pkg-squid-0.4.15
pfSense-repo-2.3.b.20160304.0222

Thanks in advance

You'll have to capture some traffic and see what it is.

And try shutting down squid to see if it stops.

Cosmetic thing "\n"  on line 206 (browser source) 151 line in snort_blocked.php file on Blocked tab