From nobody Wed Sep 17 03:24:27 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 4cRPKK738Gz686my for ; Wed, 17 Sep 2025 03:25:09 +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 4cRPKK0MTPz3TrJ for ; Wed, 17 Sep 2025 03:25:08 +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=oiMAvn3o; dmarc=none; spf=pass (mx1.freebsd.org: domain of cross+freebsd@relay.distal.com designates 168.235.95.80 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=HkRqg1X+t8RLyQt3O5cqXVyZ2mH3ti9W40229aoGQgw=; b=oiMAvn3o63sHL6H/o1EndNdRoptOY5YpI/ubTe4i0Du31f4dM1Z9kDJkjKx58Q07HVqdWD3v5C5qL9LcbnO+N+TKQSr41lhYypWD2Ien9HFjV6tiol7HOPuuqv8Glu7Fugrkl1Ur6j2Dig4AdTzxRHK2aOJjNHtGARvQYbNoBxZ6vP/tkXd1SMp2hwHEZ0jMh9uHeIyHI1H2kkjXs2fUlWDg9LxTYFfqBvHoDWE32mIpADNLaKv1+FnP6E DUGDpduTe/1nDctqPAh1V/cIQLgTFMpzxkIV68ihN/L3azn7eiDtCtRMXU1hoIL1TUvfHnhzXNpZvxXBMNiGayx0BAcA== 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 03:25:00 +0000 Received: from smtpclient.apple (magrathea.distal.com [206.138.151.12]) by tristain.distal.com (OpenSMTPD) with ESMTPSA id e212a1cf (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Tue, 16 Sep 2025 23:24:58 -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 X-Priority: 3 (Normal) In-Reply-To: <55365E3D-B7EA-4F95-BC1E-92910A2944EA@distal.com> Date: Tue, 16 Sep 2025 23:24:27 -0400 Cc: freebsd-net@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <90A490DE-6BF0-4EBB-97CE-ECA690E2359C@distal.com> References: <910737314.4002.1757962919189@localhost> <55365E3D-B7EA-4F95-BC1E-92910A2944EA@distal.com> To: Ronald Klop , Tom Pusateri X-Mailer: Apple Mail (2.3826.700.81) X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.19 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.994]; FORGED_SENDER(0.30)[cross@distal.com,cross@relay.distal.com]; R_SPF_ALLOW(-0.20)[+a:relay.dynu.com]; R_DKIM_ALLOW(-0.20)[relay.distal.com:s=mail]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_ALL(0.00)[]; DKIM_TRACE(0.00)[relay.distal.com:+]; FROM_HAS_DN(0.00)[]; TAGGED_FROM(0.00)[freebsd]; DMARC_NA(0.00)[distal.com]; HAS_X_PRIO_THREE(0.00)[3]; ARC_NA(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; ASN(0.00)[asn:3842, ipnet:168.235.92.0/22, country:US]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_NEQ_ENVFROM(0.00)[cross@distal.com,cross@relay.distal.com]; MIME_TRACE(0.00)[0:+]; 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: 4cRPKK0MTPz3TrJ > On Sep 15, 2025, at 18:54, Chris Ross = wrote: >=20 >> On Sep 15, 2025, at 15:01, Ronald Klop wrote: >>=20 >> Are you able to boot a 14.2 kernel? >> To split the search space in two.=20 >=20 > I could do that. What=E2=80=99s the easy way to get an unpacked 14.2 = generic amd64 kernel? Well, okay, that was something. I extracted a 14.2-RELEASE /boot/kernel = and was able to boot into it. The system came up far more properly than it = had under 14.1-RELEASE-p5 tried earlier. (Resource limits couldn=E2=80=99t = be applied in rc.subr with 14.1). But, the IPv6 routing problem still exposed = itself. Then, just to confirm, I rebooted into 14.1-RELEASE-p5 again. This was where things stopped being useful. This _also_ failed in the same way the more recent kernels had. I don=E2=80=99t _think_ I changed anything = between the last time I tested that, just selecting a different kernel from the boot menu, but this time it didn=E2=80=99t magically work. So, I = can=E2=80=99t say any longer that it=E2=80=99s necessarily a regression between 14.1p5 and = 14.3. I mean, I could try resetting my whole image to a snapshot from 14.1 (ZFS root), but I don=E2=80=99t think it=E2=80=99s worth that effort. >> On Sep 15, 2025, at 15:05, Tom Pusateri wrote: >>=20 >> I would try running the 14.3p2 system without the VLAN configuration = and a direct connection to the upstream provider hardware (no switch) = and see if the problem persists. That will determine if it=E2=80=99s a = VLAN issue. >=20 > That would be a bit of work. I have an available ix port, so I can = run a line to the machine > without vlan. It would still be a VLAN in the switch, because running = a direct line is not > possible without much rewiring and very long cables.=20 So this is my next attempt. I don=E2=80=99t know if I have the energy = for the whole thing tonight, but I=E2=80=99ll start running cables and configuring the = switch at least. See where I get. :-) Thanks all for your time, I am just more confused now. - Chris