From owner-freebsd-hackers@freebsd.org  Tue Oct  9 06:43:05 2018
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id D72D410C1D34
 for <freebsd-hackers@mailman.ysv.freebsd.org>;
 Tue,  9 Oct 2018 06:43:05 +0000 (UTC)
 (envelope-from wojtek@puchar.net)
Received: from puchar.net (puchar.net [194.1.144.90])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "puchar.net", Issuer "puchar.net" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 57CFB786AB
 for <freebsd-hackers@freebsd.org>; Tue,  9 Oct 2018 06:43:04 +0000 (UTC)
 (envelope-from wojtek@puchar.net)
Received: Received: from 127.0.0.1 (localhost [127.0.0.1])
 by puchar.net (8.15.2/8.15.2) with ESMTPS id w996h0ch042321
 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Tue, 9 Oct 2018 08:43:00 +0200 (CEST)
 (envelope-from puchar-wojtek@puchar.net)
Received: from localhost (puchar-wojtek@localhost)
 by puchar.net (8.15.2/8.15.2/Submit) with ESMTP id w996gtnK042318;
 Tue, 9 Oct 2018 08:42:55 +0200 (CEST)
 (envelope-from puchar-wojtek@puchar.net)
Date: Tue, 9 Oct 2018 08:42:55 +0200 (CEST)
From: Wojciech Puchar <wojtek@puchar.net>
To: Peter Jeremy <peter@rulingia.com>
cc: Wojciech Puchar <wojtek@puchar.net>, freebsd-hackers@freebsd.org
Subject: Re: ntpd strange problem
In-Reply-To: <20181009052924.GJ21091@server.rulingia.com>
Message-ID: <alpine.BSF.2.20.1810090841430.41943@puchar.net>
References: <alpine.BSF.2.20.1810041557330.94038@puchar.net>
 <20181005061829.GG21091@server.rulingia.com>
 <alpine.BSF.2.20.1810051122310.9032@puchar.net>
 <a31ca466-3ef6-8a66-10cc-1c24cd6dc928@FreeBSD.org>
 <alpine.BSF.2.20.1810062041490.7470@puchar.net>
 <1538855151.14264.54.camel@freebsd.org>
 <alpine.BSF.2.20.1810081315510.26846@puchar.net>
 <20181009052924.GJ21091@server.rulingia.com>
User-Agent: Alpine 2.20 (BSF 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2018 06:43:06 -0000

>> Strange but today (4 days after i restarted ntpd) it seems to be in sync
>
> A couple of suggestions:
> * (especially if you have an ADSL link): The NTP protocol assumes that
> the path between the client and server are have symmetric timing.  In

i have gigabit connectivity with low and stable delays. so it's not this.

> my experience, bulk uploads or downloads can cause significant path
> delay asymmetries, which can confuse ntpd.
> * You only have a single server and are therefore dependent on the
> trustworthiness of that server.  A few more servers could be useful.

this server is quite (actually excellently) stable and i trust it.