[Bug 264102] ntp doesn't support unprivileged ports (works with ntpdate)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264102

--- Comment #1 from Jonathan Vasquez <jon@xyinn.org> ---
I tested OpenNTPD and I can see if immediately connects to the freebsd ntp pool
(Excluding the offset adjustment since -s was removed and it's using an
"improved" variation on -s as default, although it hasn't actually fixed the
clock after many minutes. So I'll probably try and set it manually via 'date'
and I'll also check my BIOS settings:
https://undeadly.org/cgi?action=article;sid=20191111075815).

Results of base ntpd implementation:

root@leslie:~ # ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 0.freebsd.pool. .POOL.          16 p    -   64    0    0.000   +0.000   0.031


Results of OpenNTPD:

root@leslie:~ # ntpctl -s all
4/4 peers valid, constraint offset -14354s, clock unsynced, clock offset is
-14351047.182ms

peer
   wt tl st  next  poll          offset       delay      jitter
149.28.118.175 from pool 0.freebsd.pool.ntp.org
    1 10  2   11s   31s         0.502ms    30.323ms     1.555ms
204.2.134.163 from pool 0.freebsd.pool.ntp.org
    1 10  3   21s   34s         2.210ms    83.845ms     4.348ms
64.246.132.14 from pool 0.freebsd.pool.ntp.org
    1 10  2   21s   31s         2.575ms    20.227ms     2.043ms
65.100.46.166 from pool 0.freebsd.pool.ntp.org
    1 10  1   21s   31s        -1.617ms    96.042ms     3.099ms


OpenNTPD config:

It's the default other than me removing time.cloudflare.org and changing the
generic ntp pool to the freebsd ntp pool.)z

/usr/local/etc/ntpd.conf

servers 0.freebsd.pool.ntp.org
sensor *

constraint from "9.9.9.9"              # quad9 v4 without DNS
constraint from "2620:fe::fe"          # quad9 v6 without DNS
constraints from "www.google.com"      # intentionally not 8.8.8.8

-----

root@leslie:~ # /usr/local/sbin/ntpd -d                  
/var/db/ntpd.drift is empty                                   
ntp engine ready                                              
constraint reply from 9.9.9.9: offset -14349.678893        
constraint reply from 142.251.40.100: offset -14349.681551
cancel settime because offset is negative or close enough
peer 162.159.200.123 now valid
peer 38.229.62.9 now valid    
peer 138.236.128.36 now valid
peer 65.100.46.166 now valid
peer 38.229.62.9 now invalid
peer 38.229.62.9 now valid
adjusting local clock by -14349.445186s  <-- These didn't actually adjust
anything. 
adjusting local clock by -14348.500675s

-- 
You are receiving this mail because:
You are the assignee for the bug.