ntpq -p displaying unexpected refid
by rnturn from LinuxQuestions.org on (#50QNP)
I have a Slackware system at 192.168.13.1 (gort) acting as the NTP server for our LAN. It is using "pool.ntp.org" as its time source. All the workstations and servers use it in their ntp.conf settings as the sole NTP server.
On the local NTP server (192.168.13.1) I'm able to issue "ntpq -p" and get something like:
Code:# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*ns1.oninit.net 23.31.21.163 3 u 57 64 377 39.229 -2.777 2.036On most other systems on the LAN, issuing that command returns something like:
Code:# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*gort.internal.n 74.122.204.3 4 u 17 64 377 0.062 0.177 0.152where "74.122.204.3" resolves as "ns1.oninit.net". Sort of makes sense though I would have expected to see the local NTP server as the refid. But... so far, nothing really odd.
Now on a new Raspberry Pi running Stretch using a wired network connection, after I installed the NTP package, configuring it, and starting it, I saw:
Code:# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*gort.internal.n 192.111.144.114 3 u 89 64 36 0.312 73.072 11.279Since ntpd had recently been started, I suspect that the offset and jitter, while high, are normal for a newly started ntp service and will settle down over time but I have no idea whatsoever where the "192.111.144.114" address came from. I expected this to at least point back the local NTP server (gort at 192.168.13.1) and definitely not the host at "192.111.144.144". After a few minutes, though, I began seeing the following:
Code:# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*gort.internal.n 74.122.204.3 4 u 63 128 377 0.239 28.972 14.594Similar to other systems on the LAN. Except for the offset and jitter---still a bit high as shown but way down as I'm typing this.
Was seeing the "192.111.144.144" refid something that one might see while the ntpd service is "settling down" after being started?
I'm not used to seeing the NTP clients on the LAN seeing anything other than the local NTP server address in the refid. Is this a new NTP "feature"?
Nothing appears to be broken. I'm just curious about what I'm seeing and TIA for any information one can pass along to an inquiring mind...
On the local NTP server (192.168.13.1) I'm able to issue "ntpq -p" and get something like:
Code:# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*ns1.oninit.net 23.31.21.163 3 u 57 64 377 39.229 -2.777 2.036On most other systems on the LAN, issuing that command returns something like:
Code:# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*gort.internal.n 74.122.204.3 4 u 17 64 377 0.062 0.177 0.152where "74.122.204.3" resolves as "ns1.oninit.net". Sort of makes sense though I would have expected to see the local NTP server as the refid. But... so far, nothing really odd.
Now on a new Raspberry Pi running Stretch using a wired network connection, after I installed the NTP package, configuring it, and starting it, I saw:
Code:# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*gort.internal.n 192.111.144.114 3 u 89 64 36 0.312 73.072 11.279Since ntpd had recently been started, I suspect that the offset and jitter, while high, are normal for a newly started ntp service and will settle down over time but I have no idea whatsoever where the "192.111.144.114" address came from. I expected this to at least point back the local NTP server (gort at 192.168.13.1) and definitely not the host at "192.111.144.144". After a few minutes, though, I began seeing the following:
Code:# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*gort.internal.n 74.122.204.3 4 u 63 128 377 0.239 28.972 14.594Similar to other systems on the LAN. Except for the offset and jitter---still a bit high as shown but way down as I'm typing this.
Was seeing the "192.111.144.144" refid something that one might see while the ntpd service is "settling down" after being started?
I'm not used to seeing the NTP clients on the LAN seeing anything other than the local NTP server address in the refid. Is this a new NTP "feature"?
Nothing appears to be broken. I'm just curious about what I'm seeing and TIA for any information one can pass along to an inquiring mind...