From nobody Tue May 2 18:07:47 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 4Q9p344V5Gz49FQM for ; Tue, 2 May 2023 18:08:00 +0000 (UTC) (envelope-from pprocacci@gmail.com) Received: from mail-oa1-x33.google.com (mail-oa1-x33.google.com [IPv6:2001:4860:4864:20::33]) (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 4Q9p34144bz3sh9 for ; Tue, 2 May 2023 18:08:00 +0000 (UTC) (envelope-from pprocacci@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-oa1-x33.google.com with SMTP id 586e51a60fabf-18f4a6d2822so24317748fac.1 for ; Tue, 02 May 2023 11:08:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683050879; x=1685642879; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=vw7N+ksudoLjfYQKEdRCbZyErpgpkTcM00fagyoBigg=; b=Wf/nxy6PnQIJTwT65XJHjKFWUiZGbfZolQPFx/gjuDVpQBbSE6OQHp5r6JIo9JpS1J O9i0O/gmvMKwPZu1vzASC8JjnrtWg0q5xOsFtx4j3uK3BvQoIstj9WtNfN8tVhtDsS1R gvh9QPnjXD7sLCQMBYFWSm+f/r5hiqi9n/SyyWkNwLeeba0yUJSD23spWA0g7Wz+hExB iZ4aajT5ZXLhxBFj0P7VnH9AvMusY1SldoYj7w2sQrhgClnrTuaOIcfTm/KY1Es3XGU/ j8Ywb+p3QRbP2jU7FkuBgbcRQKz0VgcYPsTxmc9VYP2L/KmXB/pRkAkQp7D/9xxoPUF0 MHaw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683050879; x=1685642879; 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=vw7N+ksudoLjfYQKEdRCbZyErpgpkTcM00fagyoBigg=; b=LUOVpPLhbVsMW69pjXH+ScV/+WY/2jR8SDoTf9P6KRsBCbjyowLAQfJ+lMdNL/I0yg siCPuHudozW0TgH04epKvPiy8mypvPk9JFVACQx3OYC02jJenez+LHtNmK7wuGKtBKyO B1JJLvM+IEly7gSuIGUtq/dw7WqqtPj2pLNn0xfAs9hPAsdhcA4qVlTm+EsIJVxcS6MU EuWbIvUrsnSu8K0cZFL8eZliVh8mqKdUfIRFcLZcMMzGM2lbldjEwW8OBAZYZ5WsFLr0 2zO7zsYx6usDE4Z+1Ynejw68f2j3ck8kYBTQTs6BwFV5xaFqqDXRpNJurwG2oxnAN1AL wMGg== X-Gm-Message-State: AC+VfDy1u1GYvz1pXiWVoQsmdIM1XcEqcHdKOotDkg4zXqZqiBCy2CDn udYFkKTN6bY7xf1Tyd5vXmF3TTbaIX5S1Eymy4dJGzRUV3rK X-Google-Smtp-Source: ACHHUZ4z6Fcr/wp61G80XeNMP8QBONlgmvTQLsAeXd8r4jjkgRGhJH4NpEq+5bnt5DnWU+bdB/q6CcThLsBqX7XxP3c= X-Received: by 2002:a4a:d8d9:0:b0:541:87fe:5b75 with SMTP id c25-20020a4ad8d9000000b0054187fe5b75mr8571614oov.1.1683050878560; Tue, 02 May 2023 11:07:58 -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 14:07:47 -0400 Message-ID: Subject: Re: ntpd error on a bridged network To: Doug Denault Cc: questions@freebsd.org Content-Type: multipart/alternative; boundary="000000000000c171a005fab9d1a7" X-Rspamd-Queue-Id: 4Q9p34144bz3sh9 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2001:4860:4864::/48, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000c171a005fab9d1a7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, May 2, 2023 at 1:02=E2=80=AFPM Doug Denault wro= te: > 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. > > > _____ > Douglas Denault > http://www.safeport.com > doug@safeport.com > Voice: 301-217-9220 > Fax: 301-217-9277 > > When you restart ntpd after the system has fully booted, does the same error occur? 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? ~Paul --=20 __________________ :(){ :|:& };: --000000000000c171a005fab9d1a7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Tue, May 2, 2023 at 1:02= =E2=80=AFPM Doug Denault <doug@safeport.com> wrote:
We replaced an old apple router with a Linksys Ve= lop 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:
=C2=A0 =C2=A0 ntpd: error resolving pool 0.freebsd.pool.ntp.org: Na= me does not resolve (8)

however:

=C2=A0 =C2=A0 host -t a 0.freebsd.pool.ntp.org
=C2=A0 =C2=A0 0.freebsd.pool.ntp.org has address 174.53.169.69
=C2=A0 =C2=A0 0.freebsd.pool.ntp.org has address 192.241.155.186 =C2=A0 =C2=A0 0.freebsd.pool.ntp.org has address 38.229.53.9
=C2=A0 =C2=A0 0.freebsd.pool.ntp.org has address 38.229.57.9

=C2=A0 =C2=A0 ping -c 2 0.freebsd.pool.ntp.org
=C2=A0 =C2=A0 PING 0.freebsd.pool.ntp.org (94.237.120.208): 56 data= bytes
=C2=A0 =C2=A0 64 bytes from 94.237.120.208: icmp_seq=3D0 ttl=3D53 time=3D78= .773 ms
=C2=A0 =C2=A0 64 bytes from 94.237.120.208: icmp_seq=3D1 ttl=3D53 time=3D79= .012 ms

=C2=A0 =C2=A0 /etc/resolv.conf
=C2=A0 =C2=A0 # Generated by resolvconf
=C2=A0 =C2=A0 search boltsys.com
=C2=A0 =C2=A0 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.


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


When you restart ntpd after the system has fully boo= ted, does the same error occur?

--000000000000c171a005fab9d1a7--