Date: Tue, 2 May 2023 16:01:42 -0400 (EDT) From: Doug Denault <doug@safeport.com> To: Paul Procacci <pprocacci@gmail.com> Cc: questions@freebsd.org Subject: Re: ntpd error on a bridged network Message-ID: <alpine.BSF.2.00.2305021544520.29936@bucksport.safeport.com> In-Reply-To: <CAFbbPujQRGJ_k1N8uxW5LMYyWb9od1O8M=WgaWCW3C1O2qervA@mail.gmail.com> References: <alpine.BSF.2.00.2305021300400.29936@bucksport.safeport.com> <CAFbbPujQRGJ_k1N8uxW5LMYyWb9od1O8M=WgaWCW3C1O2qervA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <doug@safeport.com> 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.2305021544520.29936>