Oh what a problem to have, how will you cope?
On Wed, 15 Dec 2021, 21:50 Jeff Kruth via time-nuts, <
time-nuts@lists.febo.com> wrote:
> Got delivery today of our new MHM2010 Maser after 1-1/2 years It was
> delivered hot, so after a little bit of setup, the VCO gave a green light
> and the
Got delivery today of our new MHM2010 Maser after 1-1/2 years It was
delivered hot, so after a little bit of setup, the VCO gave a green light and
the status telemetry looks likes its a GO. What an amazing piece of hardware!
Beautiful too!
Still have an SAO VLG-10 to repair if possible,
Hi
One really big thing that has changed is the number of folks doing this
sort of thing via a dsl or cable modem that has > 20 ms of asymmetry.
You will not find many NTP papers studying that sort of network connection.
Bob
> On Dec 15, 2021, at 11:30 AM, Lux, Jim wrote:
>
> On 12/15/21
On 12/15/21 7:53 AM, Magnus Danielson via time-nuts wrote:
Hi,
Expect network routes to be more dispersed these days, as it is needed.
While the wedge plot is a classic for NTP, it may be interesting to
plot forward and backward path histograms independently.
Cheers,
Magnus
I assume
On 12/15/21 7:53 AM, Magnus Danielson via time-nuts wrote:
Hi,
Expect network routes to be more dispersed these days, as it is needed.
While the wedge plot is a classic for NTP, it may be interesting to
plot forward and backward path histograms independently.
Cheers,
Magnus
I assume
Hi,
Expect network routes to be more dispersed these days, as it is needed.
While the wedge plot is a classic for NTP, it may be interesting to plot
forward and backward path histograms independently.
Cheers,
Magnus
On 2021-12-15 16:25, Adam Space wrote:
Yeah I think it is localized.
Yeah I think it is localized. Network paths have been quite variable for
me. Every once in a while I start getting massive delays from the NIST
servers to my system, resulting in results like yours.
Interestingly though, time-e-g was one of the only servers that didn't have
this problem for me.
> The hardware are done by the network PHY and need 1588 support in the
driver, which is not common.
PTP HW timestamping is thankfully a bit more common than NTP one. From
which you can deduce that it's unlikely you'll get HW timestamping in NTP
context.
However, new Chrony has support for
> results are awful for time-e-g.nist.gov
That box is busted/sick. The IPv6 address is horrible.
If you want to discuss reasonably-normal operations, pick another system.
--
Nothing is ever totally useless.
It can always serve as a bad example.
--
These are my opinions. I hate spam.
