[Bug 264102] ntp doesn't support unprivileged ports (works with ntpdate)
Date: Fri, 20 May 2022 15:16:32 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264102 --- Comment #2 from Jonathan Vasquez <jon@xyinn.org> --- After manually going back into my BIOS and setting the clock again, I get the following in the base ntpd (which is good): root@leslie:~ # ntpd -q 20 May 11:12:32 ntpd[3993]: ntpd 4.2.8p15-a (1): Starting 20 May 11:12:32 ntpd[3993]: Command line: ntpd -q 20 May 11:12:32 ntpd[3993]: ---------------------------------------------------- 20 May 11:12:32 ntpd[3993]: ntp-4 is maintained by Network Time Foundation, 20 May 11:12:32 ntpd[3993]: Inc. (NTF), a non-profit 501(c)(3) public-benefit 20 May 11:12:32 ntpd[3993]: corporation. Support and training for ntp-4 are 20 May 11:12:32 ntpd[3993]: available at https://www.nwtime.org/support 20 May 11:12:32 ntpd[3993]: ---------------------------------------------------- 20 May 11:12:32 ntpd[3993]: proto: precision = 0.107 usec (-23) 20 May 11:12:32 ntpd[3993]: basedate set to 2018-08-07 20 May 11:12:32 ntpd[3993]: gps base set to 2018-08-12 (week 2014) 20 May 11:12:32 ntpd[3993]: leapsecond file ('/var/db/ntpd.leap-seconds.list'): good hash signature 20 May 11:12:32 ntpd[3993]: leapsecond file ('/var/db/ntpd.leap-seconds.list'): loaded, expire=2022-12-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37 20 May 11:12:32 ntpd[3993]: Listen and drop on 0 v6wildcard [::]:123 20 May 11:12:32 ntpd[3993]: Listen and drop on 1 v4wildcard 0.0.0.0:123 20 May 11:12:32 ntpd[3993]: Listen normally on 2 lo0 [::1]:123 20 May 11:12:32 ntpd[3993]: Listen normally on 3 lo0 [fe80::1%1]:123 20 May 11:12:32 ntpd[3993]: Listen normally on 4 lo0 127.0.0.1:123 20 May 11:12:32 ntpd[3993]: Listen normally on 5 ue0 192.168.1.148:123 20 May 11:12:32 ntpd[3993]: Listen normally on 6 wlan0 192.168.1.136:123 20 May 11:12:32 ntpd[3993]: Listen normally on 7 wg0 10.0.0.2:123 20 May 11:12:32 ntpd[3993]: Listening on routing socket on fd #28 for interface updates 20 May 11:12:33 ntpd[3993]: Soliciting pool server 96.126.122.39 20 May 11:12:34 ntpd[3993]: Soliciting pool server 107.194.210.155 20 May 11:12:42 ntpd[3993]: ntpd: time slew +0.001047 s ntpd: time slew +0.001047s ntpd -p also shows that it's properly connected: 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.000 +vps3.drown.org 68.166.61.255 2 u 23 64 1 53.505 -0.191 1.104 *50-205-57-38-st .GPS. 1 u 24 64 1 16.988 -0.075 0.970 +12.167.151.1 158.51.134.123 2 u 22 64 1 22.400 +2.056 1.694 I'm closing this since it's working. Sorry for the noise. I still think the "big jump" type of feature and the unprivileged ports is useful but given that it seems to be working without this feature, I'll close. Someone can re-open it or open a new ticket without all of these posts. -- You are receiving this mail because: You are the assignee for the bug.