On 13-04-19 01:27, Hal Murray wrote:
> I haven't had time to look carefully at the CLOCK problems. What sort of
> hardware is that running on?
Fedora 29 on x86_64 with Garmin gps18x on rs232.
Udo
___
devel mailing list
devel@ntpsec.org
Gary said:
>> Somebody on 2600:1700:6731:6c0:f2de:f1ff:fe20:1bbe is sending you
>> packets that don't make sense. Same for 68.75.8.147.
> Those two hit my hackathon server as well. But the connection is a normal
> NTPv4 exchange on UDP.
Depends on what you mean by "normal". How much did you
Yo Hal!
On Fri, 12 Apr 2019 16:27:18 -0700
Hal Murray via devel wrote:
> Somebody on 2600:1700:6731:6c0:f2de:f1ff:fe20:1bbe is sending you
> packets that don't make sense. Same for 68.75.8.147.
Those two hit my hackathon server as well. But the connection is a
normal NTPv4 exchange on UDP.
The "JUNK" stuff is for debugging NTS. The most important part is the length
at the end. It's rate limited so there shouldn't be any serious problems with
clutter in the log file - just minor potential confusion like this.
Somebody on 2600:1700:6731:6c0:f2de:f1ff:fe20:1bbe is sending you
Hello,
What to think about logging like this:
Apr 11 19:12:25 vr ntpd[3428]: JUNK: M3 V4 0/23 1 4ef 48/ 0 0 550 from
[2600:1700:6731:6c0:f2de:f1ff:fe20:1bbe]:38764, lng=1408
Apr 11 19:14:34 vr ntpd[3428]: JUNK: M3 V4 0/23 1 4ef 48/ 0 0 560 from
[2600:1700:6731:6c0:f2de:f1ff:fe20:1bbe]:38764,
