Date: Sun, 14 Sep 2025 12:38:37 -0400 From: Chris Ross <cross+freebsd@distal.com> To: Karl Denninger <karl@denninger.net> Cc: freebsd-net@freebsd.org Subject: Re: IPv6 networking problems in 14.3 Message-ID: <1780EFAC-DA9C-4593-BE37-28E7FFCE4388@distal.com> In-Reply-To: <6fce77fb-9ba8-4c7b-bb9b-0e337d91f278@denninger.net> References: <4C00D174-21FE-47C4-A30A-A382138571A5@keehole.org> <A9EBD993-D77D-49F9-9FFB-0E42EA0BEE6E@keehole.org> <DC84D8EC-B084-4AF1-B3F4-413323DA613A@distal.com> <dfa7af0c-334f-4b36-86dc-b2d75d1477d3@denninger.net> <E06E4F40-0E2C-4C4E-9C27-3BCF086347FA@distal.com> <6fce77fb-9ba8-4c7b-bb9b-0e337d91f278@denninger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Sep 14, 2025, at 12:29, Karl Denninger <karl@denninger.net> 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<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> =
metric 0 mtu 1500
=
options=3D4600703<RXCSUM,TXCSUM,TSO4,TSO6,LRO,RXCSUM_IPV6,TXCSUM_IPV6,MEXT=
PG>
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 <full-duplex>)
status: active
nd6 options=3D1<PERFORMNUD>
ix0: flags=3D1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> =
metric 0 mtu 1500
=
options=3D4e53fbb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWC=
SUM,TSO4,TSO6,LRO,WOL_UCAST,WOL_MCAST,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,R=
XCSUM_IPV6,TXCSUM_IPV6,HWSTATS,MEXTPG>
ether a4:53:0e:79:b9:82
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1780EFAC-DA9C-4593-BE37-28E7FFCE4388>