NTP not able to use ipv6 peer

[gunnarf]

So now I got the answers from the ISP "expert". They say that it must be my firewall blocking port 123.

Just plain stupidity. So I'll leave it there. I'm glad I can run ipv6 on all other services.

>:(

[bcookatpcsd]

Just wanted to add myself onto this..

using time.aws.com (opnsense is a bare metal protectli.. if it matters)

Using local unbound..

This happens and then I have to restart ntpd.. will probably switch to chrony but that brings other issues..

System / Settings / General / Prefer to use IPv4 even if IPv6 is available is checked as well

[CJ]

Just wanted to add myself onto this..

using time.aws.com (opnsense is a bare metal protectli.. if it matters)

Using local unbound..

This happens and then I have to restart ntpd.. will probably switch to chrony but that brings other issues..

System / Settings / General / Prefer to use IPv4 even if IPv6 is available is checked as well

Is there a reason you only have one time server?

I'm using the default pool entries along with having prefer ip4 checked and I see both ip6 and ip4 peers being used.

In the past I had a lot of issues with time sync because the default hwclock selection drifted too much.  Once I fixed that by changing to a more stable clock it's all been working fine.