Date: Sat, 13 Sep 2025 17:55:07 -0400 From: Keehole <pusateri@keehole.org> To: Chris Ross <cross+freebsd@distal.com> Cc: freebsd-net@freebsd.org Subject: Re: IPv6 networking problems in 14.3 Message-ID: <A9EBD993-D77D-49F9-9FFB-0E42EA0BEE6E@keehole.org> In-Reply-To: <4C00D174-21FE-47C4-A30A-A382138571A5@keehole.org> References: <4C00D174-21FE-47C4-A30A-A382138571A5@keehole.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Also, it=E2=80=99s not typical to run a VLAN on the upstream interface to yo= ur provider so that config is what I=E2=80=99m curious about. Tom > On Sep 13, 2025, at 5:52=E2=80=AFPM, Keehole <pusateri@keehole.org> wrote:= >=20 > =EF=BB=BFSending a copy of the relevant portions of /etc/rc.conf, the outp= ut of =E2=80=9Cifconfig=E2=80=9D, and =E2=80=9Cnetstat -nra=E2=80=9D, and th= e dhcpcd config file would be helpful to determine next steps. >=20 > Tom >=20 >> On Sep 13, 2025, at 4:49=E2=80=AFPM, Chris Ross <cross+freebsd@distal.com= > wrote: >>=20 >> =EF=BB=BFHello all. My primary home router is a FreeBSD 14 system, with a= n outside connection to Verizon, through a direct connection to the ONT. (i= e, no Verizon router/bridge involved). I did a bunch of work last year, run= ning 14.1, to get IPv6 working with what they provided, and it was all worki= ng alright until I upgraded the system for 14.3 a month or so ago. I notice= d some problem immediately with dhcpcd=E2=80=99s logging, which I assumed wa= s from running an older version I built myself, and I switched to the one in= ports which seemed okay (to my eyes, but I fear I may not actually have tes= ted it). >>=20 >> Tl;dr; I am not able to get IPv6 traffic in and out of my house through V= erizon. I reached out to Roy Marples, who had helped me get this all set up= using dhcpcd a year ago. But, after looking for a bit, I think it=E2=80=99= s not dhcpcd that is the problem. >>=20 >> Dhcpcd sends a router solicitation (RS) out and immediately gets an RA ba= ck, including the delegated IPv6 network I am expecting. Then, it sends a n= eighbor solicitation (NS) and never gets an answer. A few seconds later dhc= pcd reports "vlan0: fe80::3e8a:b0ff:fe3e:4dce is unreachable=E2=80=9D and be= gins the router solicitation process over. This happens every few seconds. = I=E2=80=99ve assigned the delegated networks internally, but nothing works s= ince I can=E2=80=99t send any traffic out. >>=20 >> The RA is coming from "fe80::3e8a:b0ff:fe3e:4dce=E2=80=9D on vlan0, but t= here is never a routable address: >>=20 >> % ndp -an | grep 'fe80::3e8a:b0ff:fe3e:4dce' >> fe80::3e8a:b0ff:fe3e:4dce%vlan0 (incomplete) vlan0 expired I= >>=20 >> The NS I=E2=80=99m sending is to ff02::1:ff3e:4dce, but I=E2=80=99m never= getting an answer. It looks like I=E2=80=99m never getting any NAs. I=E2=80= =99ve tried turning on effectively =E2=80=9Callow all icmpv6=E2=80=9D in my p= f.conf, and still seeing this. And the pf.conf hadn=E2=80=99t changed since= it was working in 14.1 a couple months ago. >>=20 >> Just looking for next steps now. Interfaces are all vlan interfaces on a= n ix device running at 1gb/s. Is there any known issue in 14.3-RELEASE-p1 ?= >>=20 >> Thank you. >>=20 >> - Chris >>=20 >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A9EBD993-D77D-49F9-9FFB-0E42EA0BEE6E>