Date: Wed, 3 May 2023 15:14:32 +0000 (UTC) From: doug <doug@safeport.com> To: questions@freebsd.org Subject: Re: ntpd error on a bridged network - solved Message-ID: <1fd48f26-ca84-ab40-5a2b-23afa3e8af1@safeport.com> In-Reply-To: <alpine.BSF.2.00.2305021300400.29936@bucksport.safeport.com> References: <alpine.BSF.2.00.2305021300400.29936@bucksport.safeport.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2 May 2023, 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.
Well sorta. I was able to configure ntpd to bypass what I am pretty sure is
is all do to Linksys bugs. Setting the ntpd start flag to "-4" keeps it
from uselessly trying IPV6. In ntpd.conf I changed the pool setting to be:
pool 0.north-america.pool.ntp.org iburst minpoll 5 maxpoll 12
With this ntpd works and keeps time with our internet facing servers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1fd48f26-ca84-ab40-5a2b-23afa3e8af1>