From owner-freebsd-stable@FreeBSD.ORG Wed Feb 27 14:58:38 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A0961065675 for ; Wed, 27 Feb 2008 14:58:38 +0000 (UTC) (envelope-from ptkrisada@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.224]) by mx1.freebsd.org (Postfix) with ESMTP id EC0E58FC12 for ; Wed, 27 Feb 2008 14:58:32 +0000 (UTC) (envelope-from ptkrisada@gmail.com) Received: by wr-out-0506.google.com with SMTP id 68so4231978wri.3 for ; Wed, 27 Feb 2008 06:58:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=ImEE5Gf22dWHNvZsz6g902pAQJJAeNwvNQJ+JQDHx/0=; b=nFbYHtzGXGvd1hwPEpks9u57nmy5h/5Li+WrB6GAwnhx+adgp9OFqMxkXPj97EhUUr5dT92eihGXb9ZkGxMoGcOUba/HfkbwKEmP/hH9wFmF0YnhK4Nome+1HwTK51/rAGTr5/U/YHPOtGUi54F+48rY7DWvJqJaLLy9TTuOCKs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=anaECi3dhOXaaYzweo/d4Q0qmTBbYXddfxqh+/DxH5fxBL1YKekuiostyMn/CN2Z9aSGZIX9KpJ7Yr5JGBWdsGJct3VCb4ungW4Ap2EbcBheWzU60gTZcxbTIhU8qvHg5wRjS0SCPThOFnKSiwBH57hKcxWtmUDNqM/70RdzYB8= Received: by 10.141.185.3 with SMTP id m3mr4568524rvp.167.1204124310612; Wed, 27 Feb 2008 06:58:30 -0800 (PST) Received: from gmail.com ( [125.24.106.122]) by mx.google.com with ESMTPS id c3sm18208024rvf.37.2008.02.27.06.58.24 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 27 Feb 2008 06:58:28 -0800 (PST) Date: Wed, 27 Feb 2008 21:58:28 +0700 From: Pongthep Kulkrisada To: freebsd-stable@freebsd.org Message-ID: <20080227145828.GA2091@gmail.com> Mail-Followup-To: freebsd-stable@freebsd.org References: <20080227110137.C14251065670@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080227110137.C14251065670@hub.freebsd.org> User-Agent: Mutt/1.4.2.2i Subject: Re: ntpd fails to synchronize on FreeBSD 6.3-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2008 14:58:38 -0000 > This isn't enough time. Please try this instead. > > # /etc/rc.d/ntpd stop > # /etc/rc.d/ntpdate start > > This should set your clock, even if only by a few milliseconds. > Assuming the ntpdate part is successful, continue on: > > # tcpdump -l -n -s 8192 -p "port 123" > > Now, in another window, execute: > > # /etc/rc.d/ntpd start > > Then let the tcpdump go for about 15 minutes. You aren't using the > "iburst" feature on any of the servers, so it will take some time before > they try to sync up. Alright, here is the output. Script started on Wed Feb 27 20:46:19 2008 root@bsdhost:~# /etc/rc.c/ntpd stop Stopping ntpd. root@bsdhost:~# /etc/rc.d/ntpdate start Setting date via ntp. 27 Feb 20:46:53 ntpdate[2000]: no server suitable for synchronization found root@bsdhost:~# tcpdump -l -n -s 8192 -p "port 123" tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on fxp0, link-type EN10MB (Ethernet), capture size 8192 bytes 20:51:46.149541 IP 192.168.1.10.123 > 122.154.11.67.123: NTPv4, Client, length 48 20:51:47.149369 IP 192.168.1.10.123 > 202.73.37.27.123: NTPv4, Client, length 48 20:51:48.149192 IP 192.168.1.10.123 > 133.243.238.163.123: NTPv4, Client, length 48 20:52:50.148777 IP 192.168.1.10.123 > 122.154.11.67.123: NTPv4, Client, length 48 20:52:50.148818 IP 192.168.1.10.123 > 202.73.37.27.123: NTPv4, Client, length 48 20:52:54.149147 IP 192.168.1.10.123 > 133.243.238.163.123: NTPv4, Client, length 48 20:53:53.149127 IP 192.168.1.10.123 > 202.73.37.27.123: NTPv4, Client, length 48 20:53:56.148700 IP 192.168.1.10.123 > 122.154.11.67.123: NTPv4, Client, length 48 20:53:57.149545 IP 192.168.1.10.123 > 133.243.238.163.123: NTPv4, Client, length 48 20:54:56.149586 IP 192.168.1.10.123 > 202.73.37.27.123: NTPv4, Client, length 48 20:55:02.149701 IP 192.168.1.10.123 > 122.154.11.67.123: NTPv4, Client, length 48 20:55:02.149749 IP 192.168.1.10.123 > 133.243.238.163.123: NTPv4, Client, length 48 20:56:00.148838 IP 192.168.1.10.123 > 202.73.37.27.123: NTPv4, Client, length 48 20:56:05.149070 IP 192.168.1.10.123 > 133.243.238.163.123: NTPv4, Client, length 48 20:56:07.148751 IP 192.168.1.10.123 > 122.154.11.67.123: NTPv4, Client, length 48 20:57:06.148789 IP 192.168.1.10.123 > 202.73.37.27.123: NTPv4, Client, length 48 20:57:11.148992 IP 192.168.1.10.123 > 133.243.238.163.123: NTPv4, Client, length 48 20:57:13.148718 IP 192.168.1.10.123 > 122.154.11.67.123: NTPv4, Client, length 48 20:58:10.149016 IP 192.168.1.10.123 > 202.73.37.27.123: NTPv4, Client, length 48 20:58:17.148954 IP 192.168.1.10.123 > 122.154.11.67.123: NTPv4, Client, length 48 20:58:17.148997 IP 192.168.1.10.123 > 133.243.238.163.123: NTPv4, Client, length 48 20:59:14.149296 IP 192.168.1.10.123 > 202.73.37.27.123: NTPv4, Client, length 48 20:59:22.149048 IP 192.168.1.10.123 > 122.154.11.67.123: NTPv4, Client, length 48 20:59:23.148886 IP 192.168.1.10.123 > 133.243.238.163.123: NTPv4, Client, length 48 21:00:19.149376 IP 192.168.1.10.123 > 202.73.37.27.123: NTPv4, Client, length 48 21:00:26.149309 IP 192.168.1.10.123 > 122.154.11.67.123: NTPv4, Client, length 48 21:00:29.148856 IP 192.168.1.10.123 > 133.243.238.163.123: NTPv4, Client, length 48 21:01:23.149634 IP 192.168.1.10.123 > 202.73.37.27.123: NTPv4, Client, length 48 21:01:30.149579 IP 192.168.1.10.123 > 122.154.11.67.123: NTPv4, Client, length 48 21:01:33.149117 IP 192.168.1.10.123 > 133.243.238.163.123: NTPv4, Client, length 48 21:02:29.149586 IP 192.168.1.10.123 > 202.73.37.27.123: NTPv4, Client, length 48 21:02:35.148637 IP 192.168.1.10.123 > 122.154.11.67.123: NTPv4, Client, length 48 21:02:37.149400 IP 192.168.1.10.123 > 133.243.238.163.123: NTPv4, Client, length 48 21:03:32.149004 IP 192.168.1.10.123 > 202.73.37.27.123: NTPv4, Client, length 48 21:03:40.148796 IP 192.168.1.10.123 > 133.243.238.163.123: NTPv4, Client, length 48 21:03:41.149618 IP 192.168.1.10.123 > 122.154.11.67.123: NTPv4, Client, length 48 21:04:35.149397 IP 192.168.1.10.123 > 202.73.37.27.123: NTPv4, Client, length 48 21:04:45.148898 IP 192.168.1.10.123 > 122.154.11.67.123: NTPv4, Client, length 48 21:04:46.148714 IP 192.168.1.10.123 > 133.243.238.163.123: NTPv4, Client, length 48 21:05:39.149665 IP 192.168.1.10.123 > 202.73.37.27.123: NTPv4, Client, length 48 21:05:50.148985 IP 192.168.1.10.123 > 122.154.11.67.123: NTPv4, Client, length 48 21:05:50.149032 IP 192.168.1.10.123 > 133.243.238.163.123: NTPv4, Client, length 48 21:06:44.148776 IP 192.168.1.10.123 > 202.73.37.27.123: NTPv4, Client, length 48 21:06:54.149246 IP 192.168.1.10.123 > 133.243.238.163.123: NTPv4, Client, length 48 21:06:56.148916 IP 192.168.1.10.123 > 122.154.11.67.123: NTPv4, Client, length 48 21:07:49.148879 IP 192.168.1.10.123 > 202.73.37.27.123: NTPv4, Client, length 48 21:07:58.149478 IP 192.168.1.10.123 > 133.243.238.163.123: NTPv4, Client, length 48 21:08:00.149183 IP 192.168.1.10.123 > 122.154.11.67.123: NTPv4, Client, length 48 21:09:56.149530 IP 192.168.1.10.123 > 202.73.37.27.123: NTPv4, Client, length 48 ^C 49 packets captured 230 packets received by filter 0 packets dropped by kernel root@bsdhost:~# ^D Script done on Wed Feb 27 21:10:30 2008 I also run ``/etc/rc.d/ntpd start'' on another root console right after tcpdump. Note that I appended the following lines in /etc/rc.conf and reboot prior to running ``/etc/rc.d/ntpdate start''. # grep ntpdate /etc/rc.conf ntpdate_enable="YES" ntpdate_flags="-b time.navy.mi.th asia.pool.ntp.org ntp.nict.jp" These 3 NTP servers are the same as ones in /etc/ntp.conf. And same as ones in my other machine running MS Windows. On my Windows machine behind NAT, I can always get sync with these servers. And on my FreeBSD dial-up connection, I can also get sync with these servers. But ntpdate and ntpd just don't work for the ``machine behind NAT''. Even firewall on machine and router are disabled. There must be something wrong, I don't know. Please also noted that my clock is drifted but less than 1000secs, for sure. It should not be a problem for ntpd. ...referred to ntpd(8) > > Man pages over there are all FreeBSD 6.2. > > But some timestamps dated Feb 13, 2008; but footer is still FreeBSD 6.2 > > I can confirm this on my RELENG_6 box (using 6.3). I wouldn't worry > about the footer saying 6.2. OK, thanks. I will not worry it either. > The procedure is documented in /usr/src/Makefile, and you should really > follow that. I haven't read the Handbook's documentation on what to do, > but the above seems awfully extensive for something that is described in > the Makefile (which I have used since the days of 4.x without issue). Noted, thanks. > I can't help you with anything relating to updating doc-all or your > /usr/doc tree. I'm not familiar with that, sorry. No problems, actually it is not necessary. Thanks, Pongthep