Time is out by 11 hours

Started by joneda1, January 01, 2024, 12:33:29 AM

Previous topic - Next topic
I have just set up an opnsense install on a Dell PC. I have set the timezone to my local area (Sydney, Australia). The time on the dashboard is ahead of the actual time here by 11 hours. It reads "Mon Jan 1 21:31:48 AEDT 2024" when the actual time here is "Mon Jan 1 10:31:48 AEDT 2024".
I am changing from pfsense and it displays the correct time.
Is there a way to fix this or is it intentional?

So I checked the system time in the FreeBSD shell and it was out. I changed it there and now it displays correctly in opnsense. If this is the fix then what is the purpose of the NTP servers?

Perhaps system DNS is not working? I set my NTP servers to the Canadian governments (https://nrc.canada.ca/en/certifications-evaluations-standards/canadas-official-time/network-time-protocol-ntp) and they synced up right away.

Not intentional, joneda1. I am in your time zone and syncing with 0.au.pool.org (and other options) without touching FreeBSD.

I saw a joke recently, along the lines of a sign saying "0 : the number of days since the problem was not DNS". It might be the problem as saulsutherland observed.
Deciso DEC697
+crowdsec +wireguard

Is the system time in the BIOS setup set to the current time in UTC or in your local timezone? It needs to be UTC. If the system time is too far off, ntpd refuses to sync.
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)