Messages

Following up on my own post because I have solved the issue and this may help someone else.

It turns out clock was about 25 seconds slow the Windows 11 PC I was viewing the dashboard on. I have no idea why the clock was wrong as windows was configured to set the time automatically and always was set that way.

Anyway set it to manual then straight back to automatic and the time immediately corrected it's self which resulted in the dashboard working perfectly.

So if anyone else notices the traffic graphs on the dashboard taking ages to load and then lagging check the time on your computer vs the Opnsense box.  Just to clarify it was the Windows box running slow Opnsense box clock was correct (and also set to automatically)

Not a fault with Opnsense as such but just can't get my mind around it. Running latest version 24-7-8 and recently noticed that on my main Win11 machine the Traffic Graph on the Dashboard takes ages to populate. Didn't notice this before but recently verry noticeable the rest of dashboard loads quickly as expected over a 1Gig LAN connection.

As a result I have tried various devices and browsers - as a bench mark the under reporting the traffic graphs start to populate withing 3 seconds of clicking the reporting->traffic (on all devices and browsers) so in effect immediately as the 3s includes drawing all the screen from scratch.

Using various pieces of kit all hard wired except the iPad & Mac Book with the following results on the Lobby Dashboard Traffic Graph

No VPN running ipv4 & 6 dual stack with two interfaces LAN & WAN

Win11
Opera 26s
Edge 26s

Win10
Opera 8s
Edge 8s
Chrome 8s

iPad
Safari 4s
Chrome 4s

Mac Book Air
Safari 4s
Chrome 4s

Given that everything works as expected on the two apple devices I assume it's some sort of windows issue rather than an Opnsense issue but given the CPU widget is so responsive on all devices I just don't get it.


It's so noticeable in that the the CPU graph is drawn immediately and has plotted all the way across the widget before the traffic even start to populate at all.

If the data rate WAN or LAN changes before the graph is populated with the trace the scale of the graphs changes as though it's adjusting the scale to match the data so it seems to know there is data there it's just not drawing it on the screen.

Both windows PC's and browsers work fine on every other part of Opnsense with no noticeable delay both work fine on locally hosted web pages, local speed tests and remote speed tests.

What I can't understand why the there is only a delay on the Dashboard Traffic Graph.

If anyone can explain what appears to me to be extremely strange behaviour or has any solutions I would be eternally grateful or of anyone else is seeing this please let me know.

Yes it's a shame there isn't a way to select which ones to show or conversely select which ones to hide via some check box or something. Not sure of the correct way to suggest this if anyone knows of the appropriate way to request a feature pleas point me in that direction. It's obviously a minor enhancement but it would be cool to add this feature.

I'm running 24.7.2 and the first graph on the Packets and traffic tabs is Ipsec. I'm not using Ipsec so graphs show zero no surprise there. However is there a way to make the Ipsec graphs dissapear?

I have read in the forum that if I delete the rrd files ipsec-packets.rrd & ipsec-traffic.rrd which are stored in the /var/db/rrd/ directory, they don't show on the relevent tabs so I did this and haypresto they dissapeared from the relevent tabs leaving the graphs for WAN & LAN which is what I want.

Unfortunatly they re-appeared several days ago.

Is there a way to make them disappear perminantly?

I was running 24.7.1 at the time which was an upgrade from 24.1.10 so not sure if the upgrade was an issue I did have issues with the health graphs that worked fine and occasionaly stopped updating, resetting RRD data brought them back to life. This is what promted me to do a fresh install of 24.7 I havn't tried deleting the rrd files since the fresh install.