From nobody Tue May 02 20:07:58 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 4Q9rjl1X69z49Lr1 for ; Tue, 2 May 2023 20:08:11 +0000 (UTC) (envelope-from pprocacci@gmail.com) Received: from mail-oo1-xc2f.google.com (mail-oo1-xc2f.google.com [IPv6:2607:f8b0:4864:20::c2f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q9rjk6LPBz4Fb5 for ; Tue, 2 May 2023 20:08:10 +0000 (UTC) (envelope-from pprocacci@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-oo1-xc2f.google.com with SMTP id 006d021491bc7-549d9c295dfso2520607eaf.2 for ; Tue, 02 May 2023 13:08:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683058090; x=1685650090; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=dOEk5sTjujPHmZbo1il8lL4FYwkT4G4vOzkl+VPliRE=; b=rJoJDMtqDfunzPnvfMA1ibNJfxBfpB8zoXNYqkO/iN0IgXpBFEcgCYqnE9DYdWK6mj 3xqMSB2K/Xeaele6FuNkUy9AAziR26dm0IpBeLJ4PdGNWCx62zT1oCVQWTwImSWQkFz1 eA2fRwgt44CC5TfHv53+U5L5wnkIkkPcHdx7nyfYIEs/lQh91cG0peLYky28XUVZvDca 3k9ueAnIzMtX5vATbWsEMAtvzXbd6mjoxaMxTc3geEs6pBXgbRGTYf8VRf0Tkk2iUnuJ pXA74RpteFXPqcOHK1EUsj8ngF4j7fAIrXW/V+xm87a4D49+hHnfB4Mp0usTqUzx6mWI n1xw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683058090; x=1685650090; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=dOEk5sTjujPHmZbo1il8lL4FYwkT4G4vOzkl+VPliRE=; b=gr1USPj/A8LEnF7tvCzc/LsOL2g3R/6V1t6Njm1y5WSrTYSxcBVwcTvXkimem1lk7q LH7ZHo0DXUZk2tSLLa+1UAD46Wi2pV61iQ6GyQZqKqoNGUc4QGcWk5UTpehjPZRZNqhW JL99xbO6inZRwIcuXWivhFnIS1osJILGJMP9I3j0uGApeXFCcahZmrqfhN1h3EZ2x1lw J5XkP6hkncbxOqgBuTUHB12E/IHk4qFS9D6dmhuV1+s8sU2g3ulGyYOdf032VI3l95sg NvXwiAo3HJyjuubhA9kV+3GEnzanYXtBgzH7BEhpsdZ2Sn9V9y3gMBjQnQ8ju+1vu/+E 0MAA== X-Gm-Message-State: AC+VfDyHoTkPi4Ld5OVIyNEzGICLqBGyG7LvQZHzcSh6fau0TG/HamQi uyqqwBwai7F05SNB3noAxnM8YvLp6TGnHRS1aKYrv86VqQ== X-Google-Smtp-Source: ACHHUZ41foBU2xwyS3e4ZmSp8iniyPGa7/Bz4ZDmtEQyk0ggIw3xVFSh5zVgYPYAX4HPQoslzcK7WP2WLg3y0OkWJAw= X-Received: by 2002:a4a:ea45:0:b0:547:55ad:9176 with SMTP id j5-20020a4aea45000000b0054755ad9176mr7920101ooe.2.1683058089751; Tue, 02 May 2023 13:08:09 -0700 (PDT) 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 References: In-Reply-To: From: Paul Procacci Date: Tue, 2 May 2023 16:07:58 -0400 Message-ID: Subject: Re: ntpd error on a bridged network To: Doug Denault Cc: questions@freebsd.org Content-Type: multipart/alternative; boundary="000000000000937aae05fabb7f01" X-Rspamd-Queue-Id: 4Q9rjk6LPBz4Fb5 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000937aae05fabb7f01 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, May 2, 2023 at 4:01=E2=80=AFPM Doug Denault wro= te: > 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=3D0 ttl=3D53 time=3D78= .773 ms > > 64 bytes from 94.237.120.208: icmp_seq=3D1 ttl=3D53 time=3D79= .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 Douglas, I perhaps wasn't clear. Sorry about that. What happens when you simply restart ntpd? By just restarting ntpd we can quickly isolate if the problem is with ntpd. ~Paul --=20 __________________ :(){ :|:& };: --000000000000937aae05fabb7f01 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Tue, May 2, 2023 at 4:01=E2= =80=AFPM Doug Denault <doug@safepor= t.com> wrote:
On Tue, 2 May 2023, Paul Procacci wrote:

> On Tue, May 2, 2023 at 1:02?PM Doug Denault <doug@safeport.com> wrote:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0We replaced an old apple router with a Links= ys Velop router. The apple
>=C2=A0 =C2=A0 =C2=A0 =C2=A0router was behind a Verizon router and we us= ed DHCP from Verizon on the
>=C2=A0 =C2=A0 =C2=A0 =C2=A0apple device. To duplicate the setup we conf= igured the Linksys in bridge
>=C2=A0 =C2=A0 =C2=A0 =C2=A0mode.
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0ntpd starts with the error:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0 ntpd: error resolving pool 0.freebsd.pool.ntp.org: Name does not resolve (8)
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0however:
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0 host -t a 0.freebsd.pool.n= tp.org
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0 0.freebsd.pool.ntp.org= has address 174.53.169.69
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0 0.freebsd.pool.ntp.org= has address 192.241.155.186
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0 0.freebsd.pool.ntp.org= has address 38.229.53.9
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0 0.freebsd.pool.ntp.org= has address 38.229.57.9
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0 ping -c 2 0.freebsd.pool.n= tp.org
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0 PING 0.freebsd.pool.ntp.or= g (94.237.120.208): 56 data bytes
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0 64 bytes from 94.237.120.208: = icmp_seq=3D0 ttl=3D53 time=3D78.773 ms
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0 64 bytes from 94.237.120.208: = icmp_seq=3D1 ttl=3D53 time=3D79.012 ms
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0 /etc/resolv.conf
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0 # Generated by resolvconf
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0 search boltsys.com
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0 nameserver 192.168.2.1
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0Other than ntpd I see no DNS or connectivity= issues. So far the time has
>=C2=A0 =C2=A0 =C2=A0 =C2=A0been holding at 2 seconds difference
>=C2=A0 =C2=A0 =C2=A0 =C2=A0from 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?=C2=A0 =C2=A012.4



_____
Douglas Denault
ht= tp://www.safeport.com
doug@safeport.com
Voice: 301-217-9220
=C2=A0 =C2=A0Fax: 301-217-9277

Douglas,

--000000000000937aae05fabb7f01--