Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.arch.embedded > #28047
| Path | csiph.com!weretis.net!feeder4.news.weretis.net!newsreader4.netcologne.de!news.netcologne.de!peer02.ams1!peer.ams1.xlned.com!news.xlned.com!peer01.fr7!futter-mich.highwinds-media.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!post01.iad!fx03.iad.POSTED!not-for-mail |
|---|---|
| Subject | Re: clock synchronization over IP |
| Newsgroups | comp.arch.embedded |
| References | <d5b24da2-d75b-4557-b4c1-53d587fb87a6@googlegroups.com> <62e2b060-8c06-4d78-99cf-144b9b183e88@googlegroups.com> <e54016a5-a372-424c-a7f7-4aafba5385c5@googlegroups.com> <u0kspd5gbmur73bdvpgtop8u1ci4uu790r@4ax.com> <4245ed03-69bb-423a-aee2-369e84299ebb@googlegroups.com> |
| From | Clifford Heath <no.spam@please.net> |
| User-Agent | Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 |
| MIME-Version | 1.0 |
| In-Reply-To | <4245ed03-69bb-423a-aee2-369e84299ebb@googlegroups.com> |
| Content-Type | text/plain; charset=utf-8; format=flowed |
| Content-Language | en-US |
| Content-Transfer-Encoding | 7bit |
| Lines | 9 |
| Message-ID | <o25oD.42366$9O2.4833@fx03.iad> (permalink) |
| X-Complaints-To | DMCA@thecubenet.com |
| NNTP-Posting-Date | Tue, 18 Sep 2018 11:10:12 UTC |
| Date | Tue, 18 Sep 2018 21:10:12 +1000 |
| X-Received-Bytes | 1566 |
| X-Received-Body-CRC | 3362403061 |
| Xref | csiph.com comp.arch.embedded:28047 |
Show key headers only | View raw
On 17/09/18 18:45, gp.kiwi@gmail.com wrote: > Without hardware support I suspect that kind of accuracy requires a low traffic LAN, although it's possible that it keeps trying until it achieves a really short round-trip time. NTP tries to measure the minimum round-trip time, then halve it to get the one-way time, and choose the packets that arrived quickest. It's surprisingly good even on a busy network, because it can detect that and spend longer searching for "good" round trips.
Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
clock synchronization over IP gp.kiwi@gmail.com - 2018-08-24 17:54 -0700
Re: clock synchronization over IP Paul Rubin <no.email@nospam.invalid> - 2018-08-24 18:28 -0700
Re: clock synchronization over IP wzab01@gmail.com - 2018-09-15 09:00 -0700
Re: clock synchronization over IP gp.kiwi@gmail.com - 2018-09-15 15:08 -0700
Re: clock synchronization over IP George Neuner <gneuner2@comcast.net> - 2018-09-16 08:49 -0400
Re: clock synchronization over IP gp.kiwi@gmail.com - 2018-09-17 01:45 -0700
Re: clock synchronization over IP George Neuner <gneuner2@comcast.net> - 2018-09-17 11:30 -0400
Re: clock synchronization over IP gp.kiwi@gmail.com - 2018-09-17 15:04 -0700
Re: clock synchronization over IP George Neuner <gneuner2@comcast.net> - 2018-09-17 22:10 -0400
Re: clock synchronization over IP graeme.prentice@gmail.com - 2018-09-18 04:23 -0700
Re: clock synchronization over IP Andrew Smallshaw <andrews@sdf.org> - 2018-09-18 13:19 +0000
Re: clock synchronization over IP Mikko OH2HVJ <mikko.syrjalahti@nospam.fi> - 2018-09-19 18:56 +0300
Re: clock synchronization over IP upsidedown@downunder.com - 2018-09-22 11:51 +0300
Re: clock synchronization over IP Clifford Heath <no.spam@please.net> - 2018-09-18 21:10 +1000
Re: clock synchronization over IP Chris <xxx.syseng.yyy@gfsys.co.uk> - 2018-09-21 15:00 +0100
Re: clock synchronization over IP Dimiter_Popoff <dp@tgi-sci.com> - 2018-09-21 17:12 +0300
Re: clock synchronization over IP Robert Wessel <robertwessel2@yahoo.com> - 2018-09-21 09:58 -0500
Re: clock synchronization over IP Chris <xxx.syseng.yyy@gfsys.co.uk> - 2018-09-21 16:26 +0100
Re: clock synchronization over IP Chris <xxx.syseng.yyy@gfsys.co.uk> - 2018-09-21 16:02 +0100
Re: clock synchronization over IP George Neuner <gneuner2@comcast.net> - 2018-09-21 17:15 -0400
Re: clock synchronization over IP Chris <xxx.syseng.yyy@gfsys.co.uk> - 2018-09-21 22:35 +0100
Re: clock synchronization over IP "gp.kiwi@gmail.com" <graeme.prentice@gmail.com> - 2018-09-21 15:16 -0700
Re: clock synchronization over IP Chris <xxx.syseng.yyy@gfsys.co.uk> - 2018-09-22 00:11 +0100
Re: clock synchronization over IP "gp.kiwi" <graeme.prentice@gmail.com> - 2018-09-21 16:35 -0700
Re: clock synchronization over IP Chris <xxx.syseng.yyy@gfsys.co.uk> - 2018-09-22 14:19 +0100
Re: clock synchronization over IP gnuarm.deletethisbit@gmail.com - 2018-09-22 07:22 -0700
Re: clock synchronization over IP graeme.prentice@gmail.com - 2018-09-21 19:40 -0700
Re: clock synchronization over IP George Neuner <gneuner2@comcast.net> - 2018-09-21 22:17 -0400
Re: clock synchronization over IP Chris <xxx.syseng.yyy@gfsys.co.uk> - 2018-09-22 13:58 +0100
Re: clock synchronization over IP Brett <ggtgp@yahoo.com> - 2018-09-22 18:50 +0000
Re: clock synchronization over IP upsidedown@downunder.com - 2018-09-22 11:56 +0300
Re: clock synchronization over IP gnuarm.deletethisbit@gmail.com - 2018-09-22 07:31 -0700
Re: clock synchronization over IP upsidedown@downunder.com - 2018-09-22 20:02 +0300
Re: clock synchronization over IP gnuarm.deletethisbit@gmail.com - 2018-09-22 14:40 -0700
Re: clock synchronization over IP gnuarm.deletethisbit@gmail.com - 2018-09-22 07:06 -0700
Re: clock synchronization over IP Mikko OH2HVJ <mikko.syrjalahti@nospam.fi> - 2018-09-22 20:16 +0300
Re: clock synchronization over IP Chris <xxx.syseng.yyy@gfsys.co.uk> - 2018-09-22 22:22 +0100
csiph-web