From owner-freebsd-questions@FreeBSD.ORG Thu Apr 9 16:04:05 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AA791F93 for ; Thu, 9 Apr 2015 16:04:05 +0000 (UTC) Received: from bede.qeng-ho.org (bede.qeng-ho.org [217.155.128.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 341E2E69 for ; Thu, 9 Apr 2015 16:04:03 +0000 (UTC) Received: from arthur.home.qeng-ho.org (arthur.home.qeng-ho.org [172.23.1.2]) by bede.home.qeng-ho.org (8.14.9/8.14.7) with ESMTP id t39G41ju005118 for ; Thu, 9 Apr 2015 17:04:01 +0100 (BST) (envelope-from freebsd@qeng-ho.org) Message-ID: <5526A2F1.5030609@qeng-ho.org> Date: Thu, 09 Apr 2015 17:04:01 +0100 From: Arthur Chance User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: FreeBSD-Questions Subject: NTP peering broken since recent security update? Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Apr 2015 16:04:05 -0000 I have three NTP servers on my internal networks. Each of them uses various external machines as servers but they also peer with the other two internal ones to give some resilience in case the outside world goes away. Since the update and restart associated with FreeBSD-SA-15:07.ntp the ntpd processes appear to be unable to see peers (reach = 0) although they're locking onto the servers quite happily. Anyone else seeing this? -- Those who do not learn from computing history are doomed to GOTO 1