From nobody Fri Feb 21 23:15:04 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 4Z05ZT3n5Lz5pX5R for ; Fri, 21 Feb 2025 23:15:13 +0000 (UTC) (envelope-from roy@marples.name) Received: from sender2-of-o51.zoho.eu (sender2-of-o51.zoho.eu [136.143.171.51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z05ZS619lz3QQM for ; Fri, 21 Feb 2025 23:15:12 +0000 (UTC) (envelope-from roy@marples.name) Authentication-Results: mx1.freebsd.org; none ARC-Seal: i=1; a=rsa-sha256; t=1740179706; cv=none; d=zohomail.eu; s=zohoarc; b=eOHi/ZLgpIGlzTAU3ivEcCL6WfLYhk77W1VK5wlWrKsB48SaqG5wuWQk3cSWIoAyLRcUbMcWtGgXqNIA4YSCN+ur0m2p/ot6Uh8xfk90HJ5PtxKnthxY11Njf32V019msgfKLY+aDVq7oGX8A9xYO8r0f+j+ebMSlP/EZ8VCk7g= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.eu; s=zohoarc; t=1740179706; h=Content-Type:Content-Transfer-Encoding:Cc:Cc:Date:Date:From:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:Subject:To:To:Message-Id:Reply-To; bh=O7sOyj3MbZ4Pp6aEA2H3lsC2btGrqFwgpIdPXaqvIWk=; b=PFMhAYS9S53TV1N0kylYT5+Pg8BxJyQhOcMY2QWNLNnHmR3Tf9pGljNpA9LREA0OXYbI4wMz7HP5M+ybdQ9zC9akz4jjMFFZQ+aK/dQ47h0L/D9SIiGSawGnLB9Ab79UOiN71Y7tWfc8EnVyMYlzRCpBKgLUm2hxF9wkGDMmJFE= ARC-Authentication-Results: i=1; mx.zohomail.eu; dkim=pass header.i=marples.name; spf=pass smtp.mailfrom=roy@marples.name; dmarc=pass header.from= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1740179706; s=zmail; d=marples.name; i=roy@marples.name; h=Date:Date:From:From:To:To:Cc:Cc:Message-ID:In-Reply-To:References:Subject:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-Id:Reply-To; bh=O7sOyj3MbZ4Pp6aEA2H3lsC2btGrqFwgpIdPXaqvIWk=; b=a4cfsVnzP7Hf/cw1pVeIyVTabJ1DbRR1BYnao1sVskSKg90I3QOZdNmEEdWan9rw qfxtd1+MAHM+c0+dyASMJcGaCnxTMOvV2Ptyfajoibcn43AWwj0uGWl4cpluXrpKVpO WxGc0o4P01DwGlPSGRnUgeMpnSbb+g2PQ57ROlHs= Received: from mail.zoho.eu by mx.zoho.eu with SMTP id 1740179704635602.0567687641075; Sat, 22 Feb 2025 00:15:04 +0100 (CET) Date: Fri, 21 Feb 2025 23:15:04 +0000 From: Roy Marples To: "Karl Denninger" Cc: "freebsd-net" Message-ID: <1952acb0b0e.fd4954ed158194.4931129176474235446@marples.name> In-Reply-To: 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> Subject: Re: rtadvd(8) How to IPv6 tokenize interface identifier 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 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Importance: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:41913, ipnet:136.143.170.0/23, country:CH] X-Rspamd-Queue-Id: 4Z05ZS619lz3QQM X-Spamd-Bar: ---- ---- On Fri, 21 Feb 2025 22:59:15 +0000 Karl Denninger wrote ---=20 > On 2/21/2025 14:18, Roy Marples wrote: > Aha! ---- On Fri, 21 Feb 2025 18:34:25 +0000 Roy Marples = wrote --- > ---- On Fri, 21 Feb 2025 17:49:28 +0000 K= arl Denninger 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