From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ww0-f47.google.com (mail-ww0-f47.google.com [74.125.82.47]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 04445200ABA for ; Fri, 23 Sep 2011 02:09:06 -0700 (PDT) Received: by wwe5 with SMTP id 5so2828646wwe.28 for ; Fri, 23 Sep 2011 02:09:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=1kHDetpkBQcvihFNwkpYqcgdtUBYDyKbNk+A7RFyEHM=; b=laNGzRWZU/PiDZzfhMmv+/AUIW3Mdwn1Z7RGmpJwV4NVjP86vVTdEUooAtW6XhtG9Z +JnjgVST2emycnlmeNNhGhCPX4tUX1ZjVYB+uG3oL5uRgbpB29UqlpBJk89jcWm2DL/C qt0lfJt5GwVb4m+3x61G2+wJO2xuyOs3qZuTA= Received: by 10.227.201.130 with SMTP id fa2mr3433627wbb.13.1316768944405; Fri, 23 Sep 2011 02:09:04 -0700 (PDT) Received: from [192.168.1.6] (68.3-64-87.adsl-dyn.isp.belgacom.be. [87.64.3.68]) by mx.google.com with ESMTPS id n21sm15460613wbp.2.2011.09.23.02.09.03 (version=SSLv3 cipher=OTHER); Fri, 23 Sep 2011 02:09:03 -0700 (PDT) Message-ID: <4E7C4CAE.8020709@gmail.com> Date: Fri, 23 Sep 2011 11:09:02 +0200 From: Jan Ceuleers User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.21) Gecko/20110831 Thunderbird/3.1.13 MIME-Version: 1.0 To: bloat-devel@lists.bufferbloat.net Subject: Re: Preliminary results of using GPS to look for clock skew References: <20110921230205.2275820C2E5@snark.thyrsus.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: bloat-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Developers working on AQM, device drivers, and networking stacks" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Sep 2011 09:09:07 -0000 On 09/22/2011 02:18 AM, Dave Taht wrote: > Two ideas here: > > 1) Run the router WITHOUT ntp enabled at all > (and/or testing against CLOCK_REALTIME) > It would be good to know how much the base clock drift is, without > correction. Note that ntpd has infrastructure for measuring the drift: use the driftfile setting in the config file and ntpd will periodically write the drift in ms to it. Jan