Traffic Graph in Lobby Strange Behaviour

[JDabbs]

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.

[JDabbs]

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)

[va176thunderbolt]

Windows 11 doesn't update the clock very often by default:
https://www.elevenforum.com/t/how-often-should-clock-synchronize.1181/

Coupled with pc vendors cutting g cost corners and using the less than stable oscillators on the system board leads to clock drift in windows.

I adjust mine every hour, unless I need something more precise. Should keep your drift within a second or two at most.

Adam

[vpx23]

Thanks, after updating my OPNsense I noticed this bug too. My clock was running 22 seconds in advance. Was fixed after updating the time.

Anybody else noticed weird behaviour of Windows 11 23H2 after the KB5048685 update?

After the login screen I get a black screen for some seconds and the loading of the taskbar is very delayed.

Also high CPU from "Service host DCOM server process launcher" and wsappx. I locked my Windows 11 to 23H2 because of all the AI crap in 24H2 like Copilot and Recall but maybe I have to switch to FreeBSD sooner than I planned. :)