From nobody Tue Sep 17 18:46:05 2024 X-Original-To: freebsd-net@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 4X7W2m2T2Sz5VcR3 for ; Tue, 17 Sep 2024 18:46:24 +0000 (UTC) (envelope-from cross+freebsd@relay.distal.com) Received: from relay.wiredblade.com (relay.wiredblade.com [168.235.105.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4X7W2k70nTz3xYl for ; Tue, 17 Sep 2024 18:46:22 +0000 (UTC) (envelope-from cross+freebsd@relay.distal.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=relay.distal.com header.s=mail header.b=qRA+bOAb; dmarc=none; spf=pass (mx1.freebsd.org: domain of cross+freebsd@relay.distal.com designates 168.235.105.136 as permitted sender) smtp.mailfrom=cross+freebsd@relay.distal.com dkim-signature: v=1; a=rsa-sha256; d=relay.distal.com; s=mail; c=relaxed/relaxed; q=dns/txt; h=From:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type:Content-Transfer-Encoding:In-Reply-To:References; bh=Pn/eJZdyNJIEEntDSjQ8mjcEeNyRT6xnY68ZeIw/ZF8=; b=qRA+bOAbGmTyGUoj6bKztSeDE+bea32MMdmjsRjp5lChgdOQ+9prOtfDFOOMrkQRrfb/aFaxciCt5QjuAuYDfYec3T/ozkFFxGEKlIcsMs+HYMPpGT3skhijsaZRUh+5olslWruOpUBMcDIUtocMbSURNCCchoUh5aM3MRmICgsx6tTcimYfaUKDk2QVFj5gNRIVY1nHsTZ/U8EizMPcNHlMzUm0GP42oBmnHVN6lcTNnLwdDCQY6ZK5cN Aass8qZUyh/avFgAIIQcD5zEgd20ISA8VF30X9An5sqhp2tivNnL+kmxXWOoElP63IeMOHPN/7u3wuiatHLPW4/6pDAA== Received: from mail.distal.com (pool-108-51-233-124.washdc.fios.verizon.net [108.51.233.124]) by relay.wiredblade.com with ESMTPSA (version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256) ; Tue, 17 Sep 2024 18:46:19 +0000 Received: from smtpclient.apple ( [173.38.117.78]) by tristain.distal.com (OpenSMTPD) with ESMTPSA id 80e48d99 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Tue, 17 Sep 2024 14:46:17 -0400 (EDT) Content-Type: text/plain; charset=utf-8 List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51\)) Subject: Re: IPv6 neighbor flaps for ISP router are occurring frequently From: Chris Ross In-Reply-To: <6CFC398B-BC5C-4CFC-8733-8D9732B121CA@distal.com> Date: Tue, 17 Sep 2024 14:46:05 -0400 Cc: freebsd-net@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <89F4F5A4-E3D9-4A43-84F6-908E3FA221A6@distal.com> <83BCC913-3375-4847-B720-5F06D76F6646@distal.com> <6CFC398B-BC5C-4CFC-8733-8D9732B121CA@distal.com> To: Karl Denninger X-Mailer: Apple Mail (2.3776.700.51) X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.18 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.979]; FORGED_SENDER(0.30)[cross@distal.com,cross@relay.distal.com]; R_DKIM_ALLOW(-0.20)[relay.distal.com:s=mail]; R_SPF_ALLOW(-0.20)[+a:relay.dynu.com]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_ALL(0.00)[]; TAGGED_FROM(0.00)[freebsd]; DMARC_NA(0.00)[distal.com]; RCPT_COUNT_TWO(0.00)[2]; DKIM_TRACE(0.00)[relay.distal.com:+]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2]; FROM_NEQ_ENVFROM(0.00)[cross@distal.com,cross@relay.distal.com]; ASN(0.00)[asn:3842, ipnet:168.235.104.0/22, country:US]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-net@freebsd.org]; APPLE_MAILER_COMMON(0.00)[]; TO_DN_SOME(0.00)[] X-Rspamd-Queue-Id: 4X7W2k70nTz3xYl > On Sep 16, 2024, at 18:02, Chris Ross = wrote: >=20 > Build was from releng/14.1 back at the start of August. Looking > now, I see that I=E2=80=99m behind by 24 commits, so maybe should try > updating. Hmm. Well, I updated my releng/14.1 tree and built a new kernel last = night. I rebooted and after dhcpcd started up it was emitting the same notices for many hours. But, at about 07:30 this morning it stopped. It=E2=80=99= s now been 7 hours since there have been any such notices from dhcpcd. And, I = can=E2=80=99t think of what couple. hanged. dhcpcd has been running for 15+ hours, complained for 8 hours, then stopped for 7. I=E2=80=99ll keep an eye on = it, but suffice to say I=E2=80=99m perplexed. - Chris