From owner-freebsd-stable@FreeBSD.ORG Thu Feb 28 14:02:18 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 934AD106566C for ; Thu, 28 Feb 2008 14:02:18 +0000 (UTC) (envelope-from ptkrisada@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.227]) by mx1.freebsd.org (Postfix) with ESMTP id 34AAA8FC19 for ; Thu, 28 Feb 2008 14:02:18 +0000 (UTC) (envelope-from ptkrisada@gmail.com) Received: by wr-out-0506.google.com with SMTP id 68so5200772wri.3 for ; Thu, 28 Feb 2008 06:02:17 -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=LQwJO1Yi5NNl0yoOj4ktpDvmzXNBOXUjn+zaTtXAgo4=; b=A0n1Dw8F6ScwpdiX5RTNGhPk58QLJx64/XG7UfQ5CFK3+7TNcshnzEul9iX1c6uZu3/6H7RSFSszt+NgIMa/sgRN1ffHyzIpPVMCwEH+cuk7TToj7PA1mAjGwrcfMuiDgGuzUySOpUMK3irGsynlLZhru7espouHVg7XE7lP3Fc= 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=CqPn/PaqAwdogRpFECpHhAfaNCPaGl8q5FB/GS+rEkt1rwwzMJQm0bmh0eSndpc3lB339dAasX0wiYAPb6ZZWTuT4CcZc0PoKw+O7bAGylWHlI/82W08knZFfAfzq0NV8RTggdPS+2RbB4+xD1ue0iMdD5rBSPGOsViSpYi6EjM= Received: by 10.141.63.20 with SMTP id q20mr5460911rvk.258.1204207336195; Thu, 28 Feb 2008 06:02:16 -0800 (PST) Received: from gmail.com ( [125.25.182.11]) by mx.google.com with ESMTPS id f10sm20669201rvb.17.2008.02.28.06.02.11 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 28 Feb 2008 06:02:14 -0800 (PST) Date: Thu, 28 Feb 2008 21:02:20 +0700 From: Pongthep Kulkrisada To: freebsd-stable@freebsd.org Message-ID: <20080228140220.GA890@gmail.com> Mail-Followup-To: freebsd-stable@freebsd.org References: <20080227213340.8723D106567D@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080227213340.8723D106567D@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: Thu, 28 Feb 2008 14:02:18 -0000 > You're not getting responses back from __any__ of those NTP servers. If > you have a firewall *in front* of your BSD box (meaning a separate box, > not ipfw/ipfilter/pf on the same BSD box!), then this is likely the > cause of the problem. The question is that two weeks ago, with same machine, same gateway, same NAT and same firewall config, when I was on FreeBSD 6.2-RELEASE and behind NAT, I could sync with ALL IPv6 servers (IPv4 is not functioning there) I said that in my first post. I'm pretty sure that if I went back to 6.2 even behind NAT, I could get sync with IPv6. Long writing since my first post I shall summarize my events here for better understanding, and sorry for redundancy. 1. FreeBSD 5.4-RELEASE(dial up) - can sync all servers 2. FreeBSD 6.2-RELEASE(dial up) - can sync all servers 3. FreeBSD 6.2-RELEASE(NAT) - can sync IPv6 servers 4. FreeBSD 6.3-STABLE (NAT) - not sync at all The issue is the different result between 3. and 4. It seems something different between 6.2-RELEASE and 6.3-STABLE. But today I hear good news for issuance of 7.0-RELEASE. I shall go on with the new RELEASE. My bad news is I've just updated to 6.3 for 2 weeks. :-( > If not, there's two explanations: > > * Your uplink provider is filtering incoming packets destined to your > network on port 123. It works with IPv6 on 6.2 behind NAT. So this reason might not be the case. IPv4 or IPv6 bind() the same port (123). In addition, I look in ntpdate/ntpd source code. They both use datagram socket (UDP). But only ntpd support AF_INET6 address family. So in my case ntpdate, which supports only IPv4, will never work on my system even on 6.2 behind NAT. > * If you're using NAT on this BSD box, somehow your NAT rules are > broken, or you're doing something bizarre with network interfaces. I'm not using BSD box as a router. > You also confirm this by stating that you're able to talk to NTP servers > if you use a dial-up connection on the same box, so it really sounds > like you have a NAT problem and not an NTP problem. Probably, but I'm not quite sure as my reason above. Thanks, Pongthep