NTP not working

3

Hi,

Thanks! no way :joy: you redirected me to my own post but on another forum.

Unfortunately, the router in bridge mode is not an option for now.

I was mainly looking for guidance on LAN/WAN/NAT rules that could be interfering without me realising it, rather than a network-level solution, or perhaps if there is some peculiarity of the NTP protocol that we were overlooking. Or a way to diagnose it.

The tcpcump of the interface doesn’t say much, and this command:

ntpdate -dv 0.es.pool.ntp.org

has this output:

erver 212.227.145.233, port 123
stratum 2, precision -24, leap 00, trust 000
refid [152.78.229.49], root delay 0.036499, root dispersion 0.037933
reference time:      ed2f082e.0567378f  Thu, Feb  5 2026 13:14:38.021
originate timestamp: ed2f0db7.430a798f  Thu, Feb  5 2026 13:38:15.261
transmit timestamp:  ed2f0db6.707ebb4b  Thu, Feb  5 2026 13:38:14.439
filter delay:  0.04776    0.04517    0.05122    0.04518
               ----       ----       ----       ----
filter offset: +0.813946  +0.812655  +0.815561  +0.812643
               ----       ----       ----       ----
delay 0.04517, dispersion 0.00067, offset +0.812655

 5 Feb 13:38:14 ntpdate[42776]: step time server 172.233.111.111 offset +0.805528 sec

however, this other one:

root@opnsense:~ # ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 0.es.pool.ntp.o .POOL.          16 p    -   64    0    0.000   +0.000   0.000
 1.es.pool.ntp.o .POOL.          16 p    -   64    0    0.000   +0.000   0.000
 2.pool.ntp.org  .POOL.          16 p    -   64    0    0.000   +0.000   0.000

On the other hand, I’m still waiting for my ISP to respond regarding forwarding UDP port 123 inbound from my router’s WAN to OPNsense.

I also checked this post link, and I also get “ntpd exiting on signal 15 (Terminated)” :pensive_face: