These restrictions include, but are not limited to: When selecting a publicly accessible NTP server, it is important to follow the access guidelines provided by the server. If you are lucky enough to make due with the latencies and higher error associated with Internet NTP servers we have a few pointers. Asymmetric routes and network congestion can cause errors of 100 ms or more.” That sure sounds like a compelling use of local NTP servers for timing critical applications, right?! These cases are where having your own NTP server synchronized to GPS time can be essential.Īccording to Wikipedia, “NTP can usually maintain time to within tens of milliseconds over the public Internet, and can achieve better than one millisecond accuracy in local area networks under ideal conditions. It’s also useful for when you have a high number of client devices on the same network that require accurate synchronization. However, in high-demand, timing-critical, remotely located or bandwidth constrained applications, these may be too unreliable, or worse yet, not work at all. For example, you do not need one if you want to use the protocol and can reliably access and synchronize with 3rd party NTP servers over the internet (more on those resources below). However, any device listed as stratum 16 or greater should be considered inaccurate.įor many types of applications having your own NTP server is unnecessary. Stratum numbers can keep increasing, up to a theoretical stratum 256 device. Public, open use NTP servers often fall in to this category.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |