Help Troubleshooting OPNsense as LAN NTP Server (Service Status Pending)

[Patrick M. Hausen]

Just a tangent there are also dedicated timeserver appliances available from other vendors that do not need internet but use GPS and Radio.

Very satisfied with one of these.

[mooh]

Also, don't get carried away with the number of servers or pools. A large number of servers may not improve your results.

When choosing pools, it's best to learn what type of servers they're bundling. For me, I have chosen 2.de.pool.ntp.org because it includes IPv6 servers and they tend to work best for me.

[Kets_One]

hi mb19,

Seems you are mixing up three possible situations:
1. LAN client requesting time from a NTP server on WAN
2. Opnsense router acting as an NTP client requesting time from an NTP server on WAN for synchronising its own clock
3. Opnsense router acting as a NTP server itself to serve time requests from LAN clients

situation 1: Appears to be working, since time of LAN client is synced.
situation 2: appears not to be working for unknown reasons. because of this, stiation 3 will also not work because of an unsynced clock on opnsense router.

From your example you say that for you can see traffic going out to WAN as well as coming back.
However, the NTPd daemon in Opnsense router does not appear to be synchronised.

Config looks ok.

[allan]

OPNsense can also do GPS, but I know of nobody using that.

I went through an NTP+GPS phase and I had this GPS connected to an RS232 port running bare metal OPNsense. There is a tunable to pull PPS from DCD and I got its offset down to below 10ns. Sadly, I had to switch to USB when I upgraded and my offset is now regularly in the 0.1-0.5ms range.

OPNsense provides NTP throughout the house and I have 2 other units on the local network for accurate NTP sync.

Code Select Expand

     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
o127.127.20.0    .GPS.            0 l   10   16  377    0.000   -0.168   0.260
 0.opnsense.pool .POOL.          16 p    -   64    0    0.000   +0.000   0.000
 1.opnsense.pool .POOL.          16 p    -   64    0    0.000   +0.000   0.000
 2.opnsense.pool .POOL.          16 p    -   64    0    0.000   +0.000   0.000
 3.opnsense.pool .POOL.          16 p    -   64    0    0.000   +0.000   0.000
+2603:3018:143b: .PPS.            1 u    9   16  377    0.563   +0.159   0.085
+192.168.1.124   192.168.1.10     2 s    8   16  377    0.262   +0.155   0.033
-23.150.40.242   204.9.54.119     2 u   37   64  377   37.326   +3.317   4.652
-2603:c020:0:836 132.163.97.4     2 u   15   64  377   68.738   +3.902   1.751
-158.51.99.19    204.9.54.119     2 u   27   64  377   33.253   +8.254   1.336
-2606:82c0:23::e 216.239.35.0     2 u   37   64  377   34.156   +4.076   2.105
-15.204.246.57   94.0.219.24      2 u   10   64  377   36.513   +3.360   1.836
+144.202.0.197   207.66.79.103    2 u   25   64  377   34.933   +3.891   1.411


[LisaMT]

I switched my ISP router to transparent bridging mode.  Then let opnsense do everything.