Date: Fri, 21 Feb 2025 23:15:04 +0000 From: Roy Marples <roy@marples.name> To: "Karl Denninger" <karl@denninger.net> Cc: "freebsd-net" <freebsd-net@freebsd.org> Subject: Re: rtadvd(8) How to IPv6 tokenize interface identifier Message-ID: <1952acb0b0e.fd4954ed158194.4931129176474235446@marples.name> In-Reply-To: <fd5224bf-45d5-4834-be80-327fe43b2da8@denninger.net> References: <20250221075300.4466057d@thor.sb211.local> <195299f4ca5.fad9d85b1235.1583279903934096331@marples.name> <2cc7ae64-c0f9-464d-8c01-86d184922ea8@denninger.net> <19529ca17d9.e2e8d5de2187.2271440699368105927@marples.name> <19529f25677.105be677d239.6010993632130942600@marples.name> <fd5224bf-45d5-4834-be80-327fe43b2da8@denninger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
---- On Fri, 21 Feb 2025 22:59:15 +0000 Karl Denninger <karl@denninger.ne= t> wrote ---=20 > On 2/21/2025 14:18, Roy Marples wrote: > Aha! ---- On Fri, 21 Feb 2025 18:34:25 +0000 Roy Marples = <roy@marples.name> wrote --- > ---- On Fri, 21 Feb 2025 17:49:28 +0000 K= arl Denninger <karl@denninger.net> wrote --- > > The issue th= at I had with it not configuring properly on a cold boot, as far as I know,= has not been addressed -- unless there are updates since you and I convers= ed on that point. > > I was never able to replicate it. It might have been= fixed, it might not have been as there have been many fixes and improvemen= ts since.But now I recall someone else did!The issue is fixed here: https:/= /github.com/NetworkConfiguration/dhcpcd/commit/c1d1a885ae469dd98533b38da3c7= 753de1597d77Basically on FreeBSD there is a rc.d script which sets the IsAR= outer flag after dhcpcd starts, hence the cold boot issue.After some chit c= hat, we decided that the check isn't really needed and the issue is thus fi= xed.Let me know if that fixed it for you or not!Good luck.Roy So jus= t to be clear (its been a minute since I've played with this!) you do: > hostname=3D"IpGw.Denninger.Net" > =20 > dhcpcd_enable=3D"YES" > =20 > # Get a primary IPv4 address on the first (near serial port) = ethernet port > # > #ifconfig_igb0=3D"inet6 -ifdisabled accept_rtadv auto_linklocal" > #ifconfig_igb0=3D"DHCP -vlanhwtso -tso -lro" <---- This is the = line I'm commenting out > #ifconfig_igb0=3D"DHCP -tso -lro" > .... > in /etc/rc.conf > (and comment out the dhcp6c lines too) > =20 > That is, I TURN OFF the "DHCP" in /etc/rc.conf and make sure the = /usr/local/etc/dhcpcd.conf file has igb0 as an allowed interface? > (If I screw the pooch on this box and can't sign into it over the = network its a pain to recover it, so I'd rather not.... ;-)) > --=20 Well, it sounds good! But I would rather you don't screw the pooch if the network fails and it's = a pain to recover :/ Saying that, you could setup a static address on the box so you can get to = it over the LAN even if dhcpcd fails. If it's the WAN interface you expect to get access over, yes that could be = an issue and I'd rather you be on site in this instance. Save the pain! Good luck Roy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1952acb0b0e.fd4954ed158194.4931129176474235446>