Mills@UDEL.EDU (05/22/87)
Folks, There seem to be lots of clockwatchers out there who are chiming on the wrong host for radio-synchronized time. Last October erstwhile radio-clock host dcn1.arpa (aka dcn-gateway.arpa) at 10.0.0.111/128.4.0.1, was moved to University of Delaware along with its dcnet (128.4) cousins; however, the WWVB radio clock was left behind and connected to host macom1.arpa (aka linkabit-gw.arpa) at 10.0.0.111/192.5.8.1. This was announced on at least two occasions to this list. The following hosts are still chiming with dcn1.arpa at its dcnet address 128.4.0.1. This host, which happens to be synchronized via UDP/NTP to radio-clock hosts macom1.arpa and umd1.umd.edu, but with somewhat reduced accuracy and reliability. The data were extracted from the log files and cover over the last week or so. These hosts should switch their chimes to macom1.arpa 192.5.8.1 or umd1.umd.edu 128.8.10.1, which is also connected to a WWVB radio clock. In particular, MILNET hosts should chime with umd1.umd.edu in any case, since that host is reachable directly via a MILNET gateway without the rough ride via the overloaded ARPANET/MILNET gateways. Host Chimes ------------------------------ [10.0.0.15] 1 [10.0.0.51] 28 [10.1.0.82] 8 [10.2.0.62] 13 [10.4.0.14] 7 [10.4.0.96] 4 [10.8.0.20] 1 [128.11.1.2] 2 [128.110.16.82] 7 [128.110.16.83] 21 [128.110.16.94] 1 [128.110.4.81] 2 [128.116.64.3] 1 [128.125.1.14] 28 [128.153.4.2] 126 [128.185.127.13] 10 [128.185.129.58] 2 [128.2.253.37] 2 [128.42.1.4] 1 [128.54.2.49] 18 [128.81.43.64] 2 [128.84.253.35] 2 [128.84.254.1] 7 [128.84.254.29] 6 [128.84.254.35] 6 [128.84.254.40] 7 [128.84.254.41] 7 [128.84.254.43] 6 [128.84.254.5] 6 [128.89.0.100] 8 [128.89.0.122] 1 [128.89.0.148] 3 [128.89.0.79] 3 [128.89.0.83] 1 [128.89.0.86] 5 [128.89.0.88] 4 [128.89.0.89] 7 [128.89.0.98] 10 [128.89.1.126] 1 [128.89.1.199] 1 [128.95.1.14] 7 [128.95.1.16] 5 [128.95.1.20] 5 [128.95.1.21] 4 [18.26.0.19] 2 [18.26.0.92] 13 [18.62.0.50] 3 [18.62.0.52] 3 [18.62.0.55] 2 [18.72.0.228] 4 [18.80.0.183] 10 [18.86.0.110] 1 [18.86.0.119] 6 [18.86.0.123] 4 [18.86.0.124] 1 [18.86.0.127] 1 [18.86.0.136] 1 [18.86.0.137] 1 [18.86.0.17] 1 [18.86.0.20] 5 [18.86.0.60] 5 [18.86.0.61] 4 [18.86.0.62] 7 [18.86.0.63] 8 [18.86.0.65] 8 [18.86.0.74] 3 [18.86.0.77] 2 [18.86.0.89] 5 [18.86.0.94] 1 [18.88.0.52] 5 [18.88.0.54] 12 [18.9.0.5] 1 [192.10.41.166] 4 [192.12.33.2] 15 [192.5.11.5] 7 [192.5.146.20] 3 [192.5.19.11] 5 [192.5.19.12] 2 [192.5.19.6] 2 [192.5.19.7] 3 [192.5.19.8] 1 [192.5.39.131] 2 [192.5.39.139] 8 [192.5.53.210] 2 [192.5.53.211] 9 [192.5.53.83] 10 [26.3.0.41] 7 [26.3.0.43] 12 [26.6.0.2] 6 [35.1.1.3] 1 [36.9.0.46] 1 The following hosts are chiming with dcnet host dcn6.arpa 128.4.0.6, which is another 9600-bps hop from dcn1.arpa. Clearly, this is a bad choice, not only because this host is farther away and less accurate, but also because the host is frequently used for program development and may have buggy software running. These clockwatchers should switch to one of the above solid players. Host Chimes ------------------------------ [10.0.0.121] 62 [10.0.0.51] 14 [10.1.0.121] 76 [128.125.1.15] 65 [128.125.1.16] 68 [128.2.253.37] 1 [128.54.0.10] 125 [128.54.2.49] 28 [128.59.16.101] 7 [128.81.43.64] 1 [128.95.1.21] 2 [192.10.41.166] 1 [192.12.33.2] 4 [192.5.39.92] 3 [26.0.0.61] 1 [26.3.0.43] 10 [26.5.0.65] 70 [26.7.0.65] 86 As you can see from the above, some of the players chime more often than others. While UDP/TIME and UDP/NTP have relatively small impact on the server resources, it probably serves no useful purpose to chime a particular host with UDP/TIME more often than once or twice per day. For accuracies better than UDP/TIME (in the order of a second or less), it is far better to use UDP/NTP, which both macom1.arpa and umd1.umd.edu support. A 4.3bsd daemon/synchronizer for UDP/NTP is available from Mike Petry (petry@trantor.umd.edu). Dave