From nobody Sun Sep 14 16:38:37 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 4cPv5M02QGz686kh for ; Sun, 14 Sep 2025 16:39:35 +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 4cPv5L5L6wz3W3w for ; Sun, 14 Sep 2025 16:39:34 +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=X26AwGSsLGF5CqV4oYCNj4qwgbgSbnzD+3ufTDTox1I=; b=oRZntIIm5yhYv0LkXcS+7EhMe7ybIPxlkyQD9ebcayUyM8qM8JDI9/rDLm/aemETG1BzleZVQjwPyHjlwO2/PkQO9W2Y0zLfLZNYRWQ5OWJWmPp63C0FQoFvfVuRATT4ruRkb3SYJFh1Vzdy2CqEIQH0ryQK31A7S6CgOhNnTHYyBC7kqzOJ+oATYD5wbTOmpVDf+njllyqpLd+LRuX1/GFvjKa5ScrXDYN5tnU4eSpKbeXWR53jPVXL9Q A41RKqriNW7iptEChN8s/2Mws/IpoBrE5eqUrrkKKnvS+69RxhdFOd/KY9JtsWxkOQvGYcj6Ma4I8zD3d1JYLijanvaw== 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) ; Sun, 14 Sep 2025 16:39:31 +0000 Received: from smtpclient.apple ( [2600:4040:2c9d:5220:b497:d844:78f8:95d6]) by tristain.distal.com (OpenSMTPD) with ESMTPSA id 5e8a668e (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Sun, 14 Sep 2025 12:39:30 -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: <6fce77fb-9ba8-4c7b-bb9b-0e337d91f278@denninger.net> Date: Sun, 14 Sep 2025 12:38:37 -0400 Cc: freebsd-net@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <1780EFAC-DA9C-4593-BE37-28E7FFCE4388@distal.com> References: <4C00D174-21FE-47C4-A30A-A382138571A5@keehole.org> <6fce77fb-9ba8-4c7b-bb9b-0e337d91f278@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: 4cPv5L5L6wz3W3w > On Sep 14, 2025, at 12:29, Karl Denninger wrote: > Rolling this around in my head some more..... what is the underlying = interface? > I ask because I saw this happen with "re" driver interfaces (both IPv4 = and 6) where it would not get an ARP map and thus couldn't see anything = at all on the outside - there were enough other screwball things going = on with the "re" driver (timeouts and similar) that I tossed that and = now run on ix and a couple of SFP+ transceivers which has been = entirely-stable (although igb also appears to work as I've gotten my = hands on a box with a couple of those and tested that too.) In my case it=E2=80=99s an ix. Connected to a 1gbps switch interface, = but an ix interface. And, the same hardware that was doing this fine a = few months ago. vlan0: flags=3D1008843 = metric 0 mtu 1500 = options=3D4600703 ether a4:53:0e:79:b9:82 inet A.B.C.D netmask 0xffffff00 broadcast A.B.C.255 inet6 fe80::6e8:e675:f359:3465%vlan0 prefixlen 64 scopeid 0x4 groups: vlan vlan: 6 vlanproto: 802.1q vlanpcp: 0 parent interface: ix0 media: Ethernet autoselect (1000baseT ) status: active nd6 options=3D1 ix0: flags=3D1008843 = metric 0 mtu 1500 = options=3D4e53fbb ether a4:53:0e:79:b9:82 media: Ethernet autoselect (1000baseT ) status: active nd6 options=3D29 > Given that arp issue I have to wonder if both are connected -- = incidentally when I was testing that unit I also tried the "native" = split IPv4/IPv6 requester for dhcp rather than dhcpcd and had the same = results, so I tend to think dhcpcd is probably not the cause. Yup. I agree. There=E2=80=99s something off at a lower level, I=E2=80=99= m just like =E2=80=9CBut I didn=E2=80=99t change anything!!!=E2=80=9D = At least, that=E2=80=99s what my head keeps telling me. :-) - Chris