From owner-freebsd-stable@freebsd.org Thu Oct 22 22:10:40 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 568C9A1C801 for ; Thu, 22 Oct 2015 22:10:40 +0000 (UTC) (envelope-from dmagda@ee.ryerson.ca) Received: from eccles.ee.ryerson.ca (eccles.ee.ryerson.ca [141.117.1.2]) (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 213AD7FD for ; Thu, 22 Oct 2015 22:10:39 +0000 (UTC) (envelope-from dmagda@ee.ryerson.ca) Received: from [192.168.2.10] (192-171-37-150.cpe.pppoe.ca [192.171.37.150]) (authenticated bits=0) by eccles.ee.ryerson.ca (8.14.9/8.14.9) with ESMTP id t9MM0on4040779 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Oct 2015 18:00:51 -0400 (EDT) (envelope-from dmagda@ee.ryerson.ca) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: Can't get ntp to work From: David Magda In-Reply-To: Date: Thu, 22 Oct 2015 18:00:47 -0400 Cc: freebsd-stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Marcin Wisnicki X-Mailer: Apple Mail (2.2104) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (eccles.ee.ryerson.ca [141.117.1.2]); Thu, 22 Oct 2015 18:00:52 -0400 (EDT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Oct 2015 22:10:40 -0000 > On Oct 18, 2015, at 08:03, Marcin Wisnicki = wrote: >=20 > My ntpd stopped synchronizing clock sometime ago (default ntp.conf). >=20 > To debug the problem I've tried running ntpdate and got strange = results: >=20 >> # ntpdate 0.freebsd.pool.ntp.org >> 18 Oct 13:53:14 ntpdate[55102]: no server suitable for = synchronization found >> =09 >> # ntpdate -u 0.freebsd.pool.ntp.org >> 18 Oct 13:53:19 ntpdate[55119]: adjust time server 193.25.222.240 = offset 0.002672 sec >=20 >=20 > This would point to broken firewall BUT: >=20 >> # nmap -p123 -sU 0.freebsd.pool.ntp.org >>=20 >> Starting Nmap 6.49BETA5 ( https://nmap.org ) at 2015-10-18 13:52 CEST >> Nmap scan report for 0.freebsd.pool.ntp.org (193.25.222.240) >> Host is up (0.027s latency). >> Other addresses for 0.freebsd.pool.ntp.org (not scanned): 94.154.96.7 = 95.158.95.123 46.175.224.7 >> rDNS record for 193.25.222.240: afrodyta.complex.net.pl >> PORT STATE SERVICE >> 123/udp open ntp >>=20 >> Nmap done: 1 IP address (1 host up) scanned in 0.64 seconds >=20 > So there is nothing blocking the traffic. >=20 > Any ideas ? Both =E2=80=9Cnmap" and =E2=80=9Cntpdate -u=E2=80=9D would use an = unprivileged, ephemeral port, while ntpd(8) and a regular run of = ntpdate(8) would use UDP 123 as the source port. Perhaps there is a = firewall issue with source ports lower than 1024?