Date: Mon, 15 Sep 2025 21:01:59 +0200 (CEST) From: Ronald Klop <ronald-lists@klop.ws> To: Chris Ross <cross+freebsd@distal.com> Cc: freebsd-net@freebsd.org, Karl Denninger <karl@denninger.net> Subject: Re: IPv6 networking problems in 14.3 Message-ID: <910737314.4002.1757962919189@localhost> In-Reply-To: <74D374DA-09B8-4533-B2EE-1AFE2AC8EFAD@distal.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Are you able to boot a 14.2 kernel? To split the search space in two. Regards, Ronald Van: Chris Ross <cross+freebsd@distal.com> Datum: 15 september 2025 20:21 Aan: Karl Denninger <karl@denninger.net> CC: freebsd-net@freebsd.org Onderwerp: Re: IPv6 networking problems in 14.3 > > > Okay. Apologies to those who like the whole thread to be in each email, but > I’m starting again here after a discovery. > > I rebooted my router after copying the 14.1p5 kernel I was running earlier, > and while the system failed to come up very well (due to 14.3 userland), I > was able to manually start up dhcpcd, the same actual binary, and it was > able to set up my IPv6 connectivity through my ISP just like before. So > there’s a regression here. Or something subtle I need to change that I > am so far missing. > > Summary: > When booted with FreeBSD 14.3-RELEASE-p2, dhcpcd gets an RA from my ISP, > sends a NS, but never gets the NA response. Therefore no outgoing packets > ever get out. > > % ndp -an | grep vlan0 > fe80::3e8a:b0ff:fe3e:4dce%vlan0 (incomplete) vlan0 1s I > fe80::6e8:e675:f359:3465%vlan0 a4:53:0e:79:b9:82 vlan0 permanent R > % tail /var/log/dhcpcd.log > Sep 15 14:03:14 [10047]: vlan0: soliciting an IPv6 router > Sep 15 14:03:14 [10047]: vlan0: sending Router Solicitation > Sep 15 14:03:14 [10047]: vlan0: Router Advertisement from fe80::3e8a:b0ff:fe3e:4dce > Sep 15 14:03:14 [10047]: vlan0: executing: /usr/local/libexec/dhcpcd-run-hooks ROUTERADVERT > Sep 15 14:03:17 [10047]: vlan0: fe80::3e8a:b0ff:fe3e:4dce is unreachable > [...] > > When booting with 14.1-RELEASE-p5, dhcpcd works as expected: > > % cat 14.1-ndp-success > fe80::3e8a:b0ff:fe3e:4dce%vlan0 3c:8a:b0:3e:4d:ce vlan0 29s R R > fe80::a653:eff:fe79:b982%vlan0 a4:53:0e:79:b9:82 vlan0 permanent R > % (lines from dhcpcd.log) > Sep 15 13:50:44 [57415]: vlan0: soliciting an IPv6 router > Sep 15 13:50:44 [57415]: vlan0: sending Router Solicitation > Sep 15 13:50:44 [57415]: vlan0: Router Advertisement from fe80::3e8a:b0ff:fe3e:4dce > Sep 15 13:50:44 [57415]: vlan0: no global addresses for default route > Sep 15 13:50:44 [57415]: vlan0: executing: /usr/local/libexec/dhcpcd-run-hooks ROUTERADVERT > Sep 15 13:50:45 [57415]: vlan0: multicasting REBIND6 (xid 0x142ec7), next in 1.1 seconds > Sep 15 13:50:45 [57415]: vlan0: REPLY6 received from fe80::3e8a:b0ff:fe3e:4dce > Sep 15 13:50:45 [57415]: vlan0: renew in 3600, rebind in 5760, expire in 7200 seconds > Sep 15 13:50:45 [57415]: vlan0: writing lease: /var/db/dhcpcd/vlan0.lease6 > Sep 15 13:50:45 [57415]: vlan0: delegated prefix 2600:4040:2c9d:5200::/56 > [...] > Sep 15 13:50:45 [57415]: vlan0: adding default route via fe80::3e8a:b0ff:fe3e:4dce > [...] > Sep 15 13:50:45 [57415]: vlan0: executing: /usr/local/libexec/dhcpcd-run-hooks REBIND6 > Sep 15 13:50:45 [56455]: forked to background > [...] > > So. What other information can I help gather? I might be able to run tcpdump > when I’m up in 14.1 kernel, though the system is kinda broken in a number of > ways. Let me know anything else I can gather to help track this regression. > > -Chris > > > > > [-- Attachment #2 --] <html><head></head><body>Are you able to boot a 14.2 kernel?<div>To split the search space in two. </div><div><br></div><div>Regards,</div><div>Ronald</div><div><br><p><small><strong>Van:</strong> Chris Ross <cross+freebsd@distal.com><br><strong>Datum:</strong> 15 september 2025 20:21<br><strong>Aan:</strong> Karl Denninger <karl@denninger.net><br><strong>CC:</strong> freebsd-net@freebsd.org<br><strong>Onderwerp:</strong> Re: IPv6 networking problems in 14.3<br></small></p><blockquote style="margin-left: 5px; border-left: 3px solid #ccc; margin-right: 0px; padding-left: 5px;"><div class="MessageRFC822Viewer do_not_remove" id="P"><!-- P --> <!-- processMimeMessage --><div class="TextPlainViewer do_not_remove" id="P.P"><!-- P.P -->Okay. Apologies to those who like the whole thread to be in each email, but<br> I’m starting again here after a discovery.<br> <br> I rebooted my router after copying the 14.1p5 kernel I was running earlier,<br> and while the system failed to come up very well (due to 14.3 userland), I<br> was able to manually start up dhcpcd, the same actual binary, and it was<br> able to set up my IPv6 connectivity through my ISP just like before. So<br> there’s a regression here. Or something subtle I need to change that I<br> am so far missing.<br> <br> Summary:<br> When booted with FreeBSD 14.3-RELEASE-p2, dhcpcd gets an RA from my ISP,<br> sends a NS, but never gets the NA response. Therefore no outgoing packets<br> ever get out.<br> <br> % ndp -an | grep vlan0<br> fe80::3e8a:b0ff:fe3e:4dce%vlan0 (incomplete) vlan0 1s I <br> fe80::6e8:e675:f359:3465%vlan0 a4:53:0e:79:b9:82 vlan0 permanent R<br> % tail /var/log/dhcpcd.log<br> Sep 15 14:03:14 [10047]: vlan0: soliciting an IPv6 router<br> Sep 15 14:03:14 [10047]: vlan0: sending Router Solicitation<br> Sep 15 14:03:14 [10047]: vlan0: Router Advertisement from fe80::3e8a:b0ff:fe3e:4dce<br> Sep 15 14:03:14 [10047]: vlan0: executing: /usr/local/libexec/dhcpcd-run-hooks ROUTERADVERT<br> Sep 15 14:03:17 [10047]: vlan0: fe80::3e8a:b0ff:fe3e:4dce is unreachable<br> [...]<br> <br> When booting with 14.1-RELEASE-p5, dhcpcd works as expected:<br> <br> % cat 14.1-ndp-success<br> fe80::3e8a:b0ff:fe3e:4dce%vlan0 3c:8a:b0:3e:4d:ce vlan0 29s R R<br> fe80::a653:eff:fe79:b982%vlan0 a4:53:0e:79:b9:82 vlan0 permanent R <br> % (lines from dhcpcd.log)<br> Sep 15 13:50:44 [57415]: vlan0: soliciting an IPv6 router<br> Sep 15 13:50:44 [57415]: vlan0: sending Router Solicitation<br> Sep 15 13:50:44 [57415]: vlan0: Router Advertisement from fe80::3e8a:b0ff:fe3e:4dce<br> Sep 15 13:50:44 [57415]: vlan0: no global addresses for default route<br> Sep 15 13:50:44 [57415]: vlan0: executing: /usr/local/libexec/dhcpcd-run-hooks ROUTERADVERT<br> Sep 15 13:50:45 [57415]: vlan0: multicasting REBIND6 (xid 0x142ec7), next in 1.1 seconds<br> Sep 15 13:50:45 [57415]: vlan0: REPLY6 received from fe80::3e8a:b0ff:fe3e:4dce<br> Sep 15 13:50:45 [57415]: vlan0: renew in 3600, rebind in 5760, expire in 7200 seconds<br> Sep 15 13:50:45 [57415]: vlan0: writing lease: /var/db/dhcpcd/vlan0.lease6<br> Sep 15 13:50:45 [57415]: vlan0: delegated prefix 2600:4040:2c9d:5200::/56<br> [...]<br> Sep 15 13:50:45 [57415]: vlan0: adding default route via fe80::3e8a:b0ff:fe3e:4dce<br> [...]<br> Sep 15 13:50:45 [57415]: vlan0: executing: /usr/local/libexec/dhcpcd-run-hooks REBIND6<br> Sep 15 13:50:45 [56455]: forked to background<br> [...]<br> <br> So. What other information can I help gather? I might be able to run tcpdump<br> when I’m up in 14.1 kernel, though the system is kinda broken in a number of<br> ways. Let me know anything else I can gather to help track this regression.<br> <br> -Chris<br> <br> </div><!-- TextPlainViewer --> <hr> </div><!-- MessageRFC822Viewer --> </blockquote><br><br><br></div></body></html>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?910737314.4002.1757962919189>