Real-time monitor traffic time incorrect

I have a time related bug that I am experiencing.

On the page Real-time monitor -> Traffic in the graph, my time is off by 5 hours, i’m assuming it’s using UTC here and not EST. I know it’s taking my NTP, and TZ settings, as I can see them on the command line, and everywhere else within the gui the time is correct.

Incorrect 1900H: Real-time monitor -> Traffic

Correct 1400h: Real-time monitor -> WAN uplinks -> wan traffic
side note: WAN is capitalized everywhere on this page, expect for wan traffic.

Thank you

1 Like

I changed the timezone for testing and couldn’t reproduce the issue. To apply the new time immediately I rebooted the device.
Real-time monitor / Traffic shows the changed time.
The WAN uplinks / wan traffic still shows the old time but I guess it takes some time until new data is grabbed.

Did you setup the timezone under system settings / general settings / timezone?

I remember an issue way back on Debian with NS8. No clue at all if NethSecurity is Debian based, just thought put it here as a reference.

1 Like

In this case I don’t think it’s about a wrong / not working timezone list.

I found that the Real-time monitor / Traffic page seems to use the timezone that is set in NethSecurity but for the Real-time monitor / WAN uplinks the timezone of my local device / browser is used.

Morning all

So this pointed me in the correct direction, didn’t solve the problem, but I can see whats going on.

So my TZ is set in the gui, i double checked it. But then the gui is reporting the incorrect time.

it’s actually 0832h.

I’ve tested a number of different TZ’s and at no point does it change. I’ll set it back to my local, and reboot and see if it takes the change then. But I would think that a change + save + apply would do the trick without having to reboot.

2 Likes

Reboot fixed the time.
Guess i had the TZ set wrong the last time it rebooted.

I guess the real questions is; If the underlining OS has the correct info, why does the GUI require a reboot to have that take effect, and how many other changes require that same thing, but are maybe more invisible than time would be?

I found here that following command corrects the time shown in the UI without rebooting:

uci get system.@system[0].timezone > /tmp/TZ

EDIT:

I opened an issue.

1 Like

No other setting needs a reboot, apart from disabling NAT helpers (reboot can be avoided, but it’s much simpler).

Date in the UI is tricky, I don’t recall the details, but it involves musl. We may try implementing the workaround found by @mrmarkuz

2 Likes