From nobody Wed Sep 17 18:20:05 2025 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 4cRnBR6LyLz67q6g for ; Wed, 17 Sep 2025 18:20:31 +0000 (UTC) (envelope-from cross+freebsd@relay.distal.com) Received: from relay.wiredblade.com (relay.wiredblade.com [168.235.95.80]) (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 4cRnBR36Dtz3tl5 for ; Wed, 17 Sep 2025 18:20:31 +0000 (UTC) (envelope-from cross+freebsd@relay.distal.com) Authentication-Results: mx1.freebsd.org; none 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=yO8ZP4BY1BJRMHw1OaoXJ7ODlG7jEO5xFmmtDRU3ApU=; b=QYyr3tS7kpGflqoxs9rZvaq1q/m7bR0x9pAcNrn1Z0uYXGpQFy+GVKYwL0c9Ye7om0NASHsOTS4QDFYWGBtkqiZJF17XI5Iqm0a9i+c412jqAYlrsoGIyYNLH3Y7dDRWzY3e7X/7gpBGoSYy7EyiyM4OvRkoFQHAA08JaHZiNIW0EpHESoIijekdjyFHV6OgYUx10zwhpeHzsOZPMbr+QL4DW02I9Sfv/xM4ow6p9R7WgzaMpodN7Gh+Jd AM2/IgEwi5OltDiWgYSp9O2C7bhpRNMsyI8PNXNdWlIXrY8dYqmdng7qvW3AC7g0Nlmqnro87CmPoy3uoLo3oGzVERXg== 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) ; Wed, 17 Sep 2025 18:20:27 +0000 Received: from smtpclient.apple ( [173.38.117.81]) by tristain.distal.com (OpenSMTPD) with ESMTPSA id 6535837a (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Wed, 17 Sep 2025 14:20:16 -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 \(3826.700.81\)) Subject: Re: IPv6 networking problems in 14.3 From: Chris Ross In-Reply-To: <611820c2-05f8-40bc-9b07-bef012183e30@denninger.net> Date: Wed, 17 Sep 2025 14:20:05 -0400 Cc: freebsd-net@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <408DE851-47FF-476E-B7F6-C7920A93DD43@distal.com> References: <910737314.4002.1757962919189@localhost> <55365E3D-B7EA-4F95-BC1E-92910A2944EA@distal.com> <90A490DE-6BF0-4EBB-97CE-ECA690E2359C@distal.com> <5D82826E-8C0F-45CF-B9FF-093FD014E73F@distal.com> <611820c2-05f8-40bc-9b07-bef012183e30@denninger.net> To: Karl Denninger X-Mailer: Apple Mail (2.3826.700.81) X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[freebsd]; ASN(0.00)[asn:3842, ipnet:168.235.92.0/22, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4cRnBR36Dtz3tl5 > On 17 Sep 2025, at 06:56, Karl Denninger wrote: >>=20 >>=20 >> Oh. So with a new interface, dhcpcd isn=E2=80=99t trying to REBIND, = so it=E2=80=99s a different >> process. I=E2=80=99m not seeing any response to the SOLICIT messages, = but I admit that I >> wasn=E2=80=99t watching the DHCPv6 ports earlier, only the ICMP6, so = this may not be >> new. >>=20 >> This is all for tonight. I=E2=80=99ll try more tomorrow. Thanks all = for your time. >>=20 >>=20 > That is precisely what it was doing here when my ISP had a hissy-fit = due to cached (on their end) association between the ONT/MAC/duid. > They said it would eventually clear (after their pltime expired -- = about 2 weeks!) but obviously that's not really an answer; as soon as = they "kicked it" on their end it came up immediately. Yeah, and I agree that=E2=80=99s possible. But, this began as soon as I = upgraded to 14.3 on August 8. Interestingly, looking at my dhcpcd.log to confirm = dates and times, I see something related to pltime. It looks like when dhcpcd starts up, it sets pltime infinity on the = local interface addresses, and then after getting the REPLY6 resets them to 7200 seconds. Even now, I=E2=80=99m noticing looking more, that while = I=E2=80=99m seeing the =E2=80=9CLL of router is unreachable=E2=80=9D from dhcpcd every few = seconds, every hour it will multicast a RENEW6, and get back a REPLY6. At which point it = will add addresses to the internal interfaces, but still the same 3 seconds later will indicate the routers LL address is unreachable. I see a few days back in March when the router was unreachable=20 intermittently, but back in a minute or so each time. And a small flap once in July. But since Aug 09, always unreachable. So, it nearly _has_ to be related to the 14.3 upgrade, although it certainly may be that 14.3 is different, not wrong, and the ISP is doing sometime unpleasant. I=E2=80=99m not sure how to test that. But, at least I=E2=80=99ve ruled out the vlan interface being the = problem, since I=E2=80=99m in exactly the same state with an ix interface to the ISP now. So, on the idea of trying to back-date the whole machine, I have ZFS snapshots of the whole root from just before the first upgrade, Aug 7/8. But in googling around, I didn=E2=80=99t see a clear = indication that I could keep where I am, try swithching to that to run for=20 a while, then switch back. If someone has a guide to doing that, respond off-list (off freebsd-net at least). I thought I=E2=80=99d = answered the kernel question, but last night showed that 14.1 kernel doesn=E2=80=99= t always work, to be sure. If I can run as 14.1 again, for a few days or weeks, it will confirm at least that it=E2=80=99s my side for sure = that=E2=80=99s changed. - Chris