On Fri, Sep 04, 2020 at 11:17:40PM +0200, Christian Weisgerber wrote:
> Otto Moerbeek:
>
> > This takes the observed issue into account,
> -snip-
>
> This works for my test case of a single peer and the two scenarios of
> "can't send query" and "port unreachable".
>
> I notice that both cases
Otto Moerbeek:
> This takes the observed issue into account,
-snip-
This works for my test case of a single peer and the two scenarios of
"can't send query" and "port unreachable".
I notice that both cases are handled very differently:
* Can't send query: ntpd keeps retrying with a fast poll
On Thu, Sep 03, 2020 at 02:33:05PM +0200, Otto Moerbeek wrote:
> On Thu, Sep 03, 2020 at 02:02:36PM +0200, Christian Weisgerber wrote:
>
> > Otto Moerbeek:
> >
> > > Currently testing this.
> >
> > For "port unreachable" replies, this caused ntpd to become unsynced, but
> > the peer still
On Thu, Sep 03, 2020 at 02:02:36PM +0200, Christian Weisgerber wrote:
> Otto Moerbeek:
>
> > Currently testing this.
>
> For "port unreachable" replies, this caused ntpd to become unsynced, but
> the peer still remains valid.
Hmm, it looks like we need to reduce trustlevel as well for the
Otto Moerbeek:
> Currently testing this.
For "port unreachable" replies, this caused ntpd to become unsynced, but
the peer still remains valid.
1/1 peers valid, clock unsynced
peer
wt tl st next poll offset delay jitter
On Tue, Sep 01, 2020 at 07:58:44PM +0200, Otto Moerbeek wrote:
> On Tue, Sep 01, 2020 at 06:33:34PM +0200, Christian Weisgerber wrote:
>
> > Even after otto@'s commit in -current...
> >
> > If no replies are received for a while due to connectivity issues
> > go into unsynced mode. The
On Tue, Sep 01, 2020 at 06:33:34PM +0200, Christian Weisgerber wrote:
> Even after otto@'s commit in -current...
>
> If no replies are received for a while due to connectivity issues
> go into unsynced mode. The existing code to check if we're unsycned
> is only done on receiving an ntp
Even after otto@'s commit in -current...
If no replies are received for a while due to connectivity issues
go into unsynced mode. The existing code to check if we're unsycned
is only done on receiving an ntp packet which does not happen if
there are connectivity issues.
... ntpd can
