> # By default, exchange time with everybody, but don't allow configuration.
> restrict -4 default notrap nomodify nopeer noquery
> restrict -6 default notrap nomodify nopeer noquery
> restrict 127.0.0.1
> restrict ::1
>From docs/includes/access-commands.txt
+noquery+;;
Deny {ntpqman} queri
Hal Murray :
>
> > The other problem is a bit more serious. I can't seem to get my ntpd to
> > report mrulist entries. This hampers testing of ntpmon; the lower window is
> > supposed to be an mrulist display. Right now I can only demonstrate the
> > upper half, the automatically-refreshing pee
On 11/25/16, Achim Gratz wrote:
> Daniel Franke writes:
>> The reference timestamp isn't really used for anything
>
> The server is supposed to return this value unchanged, so one of the BSD
> implementations of the ntp client uses this field to send random data in
> order to weed out replay and f
Daniel Franke writes:
> The reference timestamp isn't really used for anything
The server is supposed to return this value unchanged, so one of the BSD
implementations of the ntp client uses this field to send random data in
order to weed out replay and fake packets. Checking for out-of-order
rep
> That's the 'reftime' field in struct pkt. Grepping, I find...that it really
> *doesn't* seem to be used. But verifying this is confusing because there
> are other variables with reftime in their names. You should both check me
> on it.
We should scan ntp classic in case we botched something
> The other problem is a bit more serious. I can't seem to get my ntpd to
> report mrulist entries. This hampers testing of ntpmon; the lower window is
> supposed to be an mrulist display. Right now I can only demonstrate the
> upper half, the automatically-refreshing peers display.
It will p
As I expected, a first cut at ntpmon took only a couple of hours to
write. This is where we start to collect some serious benefits from
having a common back-end library for Python clients; these will
continue when we start on ntpshark.
A couple of problems stand in the way of landing ntpmon in th
Hal Murray :
>
> The comment on the tail of the call to record_raw_stats says:
> /* This will always be 0 by the time we get here */
> peer->outcount);
>
> If that "always" is correct, something is broken.
>
> outcount is a hack I added to count
The comment on the tail of the call to record_raw_stats says:
/* This will always be 0 by the time we get here */
peer->outcount);
If that "always" is correct, something is broken.
outcount is a hack I added to count lost packets.
It's supposed
Hal Murray :
> [was Re: Request for code & logic review]
>
> dfoxfra...@gmail.com said:
> > For starters, we have our four timestamps:
> > t_1, the origin timestamp, is the time according to the client at which the
> > request was sent. t_2, the transmit timestamp, is the time according to the
> >
10 matches
Mail list logo
