[ntp:hackers] NTP Development Snapshot ntp-4.2.8p3-RC1 Released
Charles Elliott
elliott.ch at comcast.net
Sun May 17 15:20:46 UTC 2015
There are three problems with ntp-4.2.8p3-RC1:
1) Suppose a client/server running ntp-4.2.8p3-RC1 is accessing time from 9
Internet stratum 1 & 2 servers. Then suppose a client on the LAN is
accessing time from the aforementioned client/server. The second client has
an incorrect Refid. For example, local computer 192.168.0.78 is synced to
clock.nyc.he.net [2001:470:0:2c8::2], whose Refid is CDMA. However, local
computer 192.168.0.100, which is synced to 192.168.0.78, shows Refid of the
sync'ed server to be dbsq0013.whservidor.com [200.98.196.212]. I checked
the packets with Wireshark (version 1.12.5); here is the actual packet
dissection:
No. Time Source Destination Protocol Length
Info
13 13:58:13.384923000 192.168.1.78 192.168.1.100 NTP 90
NTP Version 4, server
Frame 13: 90 bytes on wire (720 bits), 90 bytes captured (720 bits) on
interface 0
Ethernet II, Src: SpeedDra_99:9a:9c (00:13:3b:99:9a:9c), Dst: Evga_10:d8:8d
(00:1f:bc:10:d8:8d)
Internet Protocol Version 4, Src: 192.168.1.78 (192.168.1.78), Dst:
192.168.1.100 (192.168.1.100)
User Datagram Protocol, Src Port: ntp (123), Dst Port: ntp (123)
Network Time Protocol (NTP Version 4, server)
Flags: 0x24
Peer Clock Stratum: secondary reference (2)
Peer Polling Interval: 4 (16 sec)
Peer Clock Precision: 0.000000 sec
Root Delay: 0.0119 sec
Root Dispersion: 0.0039 sec
Reference ID: dbsq0013.whservidor.com
Reference Timestamp: May 17, 2015 13:57:09.109397000 UTC
Origin Timestamp: May 17, 2015 13:58:13.383995000 UTC
Receive Timestamp: May 17, 2015 13:58:13.384871000 UTC
Transmit Timestamp: May 17, 2015 13:58:13.384901000 UTC
Here is the grid display from Meinberg's NTP monitor program of the
client/server (192.168.0.78) sync'ed to clock.nyc.he.net:
State Remote Refid Stratum Type When Poll
Reach Delay Offset Jitter
- 2610:20:6f15:15::27 ACTS 1 Unicast server 14
32 377 17.335 2.080 1.890
* 2001:470:0:2c8::2 CDMA 1 Unicast server 20
32 377 12.245 0.437 1.542
+ ntp1.conectiv.com IRIG 1 Unicast server 13
32 377 23.803 0.220 1.860
- ntp.colby.edu GPS 1 Unicast server 18 32
377 25.221 -0.681 3.471
- time-c.nist.gov ACTS 1 Unicast server 14 32
377 17.357 1.543 2.010
nist1-pa.ustiming.org INIT 16 Unicast server
2371d 32 000 0.000 0.000 0.000
- tick.jrc.us bonehed.lcs.mit.edu 2 Unicast
server 17 32 377 16.789 0.746 1.321
- tock.jrc.us ntps11.jensenresearch.com 2
Unicast server 15 32 377 16.886 -0.354 0.151
+ static-74-104-167-114.bstnma.fios.verizon.net GPS 1
Unicast server 17 32 377 23.243 0.174 0.581
Here is the grid display from Meinberg's NTP monitor program of the LAN
client (192.168.0.100) sync'ed 192.168.0.78:
State Remote Refid Stratum Type When Poll
Reach Delay Offset Jitter
* 192.168.1.78 200.98.196.212 2 Unicast server 15 16
377 1.069 0.005 0.022
+ 192.168.1.81 192.168.1.78 3 Unicast server 14 16
377 0.419 -0.065 0.022
+ 192.168.1.1 192.168.1.78 3 Unicast server 3 16
377 0.221 0.235 0.026
Where 200.98.196.212 = dbsq0013.whservidor.com.
This error has been in NTPD for the last two release candidates.
Error 2:
Someone changed the compiler output directory from
ports\winnt\vs2013\Win32-bin\Release to
ports\winnt\vs2013\Win32-out\Release, without, as far as I know, telling
anyone. It took
hours to find that change, and not a few minutes to change the installation
script.
Error 3:
Clicking on the email release notice line
"http://archive.ntp.org/ntp4/ntp-4.2/ntp-4.2.8p3-RC1.tar.gz.md5" produces
the URL http://archive.ntp.org/ntp4/ntp-4.2/ntp-4.2.8p3-RC1.tar.gz.gz, to
which WinZip objects mightily.
Charles Elliott
> -----Original Message-----
> From: hackers [mailto:hackers-
> bounces+elliott.ch=comcast.net at lists.ntp.org] On Behalf Of NTP Public
> Services Project
> Sent: Tuesday, May 12, 2015 7:31 AM
> To: hackers at lists.ntp.org
> Subject: [ntp:hackers] NTP Development Snapshot 4.3.33 Released
>
> NTP Development Snapshot 4.3.33 is now available for download.
>
> Bug Fixes:
>
> * [Bug 2745] ntpd -x steps clock on leap second
> Do leap second stepping only of the step adjustment is beyond the
> proper jump distance limit and step correction is allowed at all.
> http://bugs.ntp.org/2745
>
> Other Changes:
>
> * 4.2.8p3-RC1
>
> Tarball:
>
> http://archive.ntp.org/ntp4/ntp-dev/ntp-dev-4.3.33.tar.gz
>
> MD5 sum:
>
> http://archive.ntp.org/ntp4/ntp-dev/ntp-dev-4.3.33.tar.gz.md5
>
> Complete ChangeLog:
>
> http://archive.ntp.org/ntp4/ChangeLog-dev
>
> Please report any bugs, issues, or desired enhancements at
> http://bugs.ntp.org/.
>
> _______________________________________________
> hackers mailing list
> hackers at lists.ntp.org
> http://lists.ntp.org/listinfo/hackers
More information about the hackers
mailing list