From nobody Tue May 02 20:01:42 2023 X-Original-To: questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Q9rZJ05Rxz49LpZ for ; Tue, 2 May 2023 20:01:44 +0000 (UTC) (envelope-from doug@safeport.com) Received: from freeport.safeport.com (freeport.safeport.com [147.160.157.114]) by mx1.freebsd.org (Postfix) with ESMTP id 4Q9rZH4dR3z49j4 for ; Tue, 2 May 2023 20:01:43 +0000 (UTC) (envelope-from doug@safeport.com) Authentication-Results: mx1.freebsd.org; none Received: from bucksport.safeport.com (bucksport.safeport.com [147.160.157.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by freeport.safeport.com (Postfix) with ESMTPS id 6C97E51D37D; Tue, 2 May 2023 16:01:42 -0400 (EDT) Date: Tue, 2 May 2023 16:01:42 -0400 (EDT) From: Doug Denault To: Paul Procacci cc: questions@freebsd.org Subject: Re: ntpd error on a bridged network In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-2042001264-1683057702=:29936" X-Rspamd-Queue-Id: 4Q9rZH4dR3z49j4 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:6405, ipnet:147.160.157.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-2042001264-1683057702=:29936 Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT On Tue, 2 May 2023, Paul Procacci wrote: > On Tue, May 2, 2023 at 1:02?PM Doug Denault wrote: > We replaced an old apple router with a Linksys Velop router. The apple > router was behind a Verizon router and we used DHCP from Verizon on the > apple device. To duplicate the setup we configured the Linksys in bridge > mode. > > ntpd starts with the error: >     ntpd: error resolving pool 0.freebsd.pool.ntp.org: Name does not resolve (8) > > however: > >     host -t a 0.freebsd.pool.ntp.org >     0.freebsd.pool.ntp.org has address 174.53.169.69 >     0.freebsd.pool.ntp.org has address 192.241.155.186 >     0.freebsd.pool.ntp.org has address 38.229.53.9 >     0.freebsd.pool.ntp.org has address 38.229.57.9 > >     ping -c 2 0.freebsd.pool.ntp.org >     PING 0.freebsd.pool.ntp.org (94.237.120.208): 56 data bytes >     64 bytes from 94.237.120.208: icmp_seq=0 ttl=53 time=78.773 ms >     64 bytes from 94.237.120.208: icmp_seq=1 ttl=53 time=79.012 ms > >     /etc/resolv.conf >     # Generated by resolvconf >     search boltsys.com >     nameserver 192.168.2.1 > > Other than ntpd I see no DNS or connectivity issues. So far the time has > been holding at 2 seconds difference > from the servers not on the office LAN. > > > When you restart ntpd after the system has fully booted, does the same > error occur? It is the same from power-off, reboot, and starting and stopping dhclient. I have also used google nameservers as well as 192.168.2.1 (verizon) all works the same. > Just trying to isolate if it's a problem with ntpd specifically or > perhaps ntpd starting before the network becomes available. > > What version of FreeBSD are you running? 12.4 _____ Douglas Denault http://www.safeport.com doug@safeport.com Voice: 301-217-9220 Fax: 301-217-9277 --0-2042001264-1683057702=:29936--