From nobody Mon Oct 6 17:11:44 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 4cgQnM6YwSz6BBpC for ; Mon, 06 Oct 2025 17:12:39 +0000 (UTC) (envelope-from cross+freebsd@relay.distal.com) Received: from relay.wiredblade.com (relay.wiredblade.com [168.235.105.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4cgQnM2b19z3spd; Mon, 06 Oct 2025 17:12:39 +0000 (UTC) (envelope-from cross+freebsd@relay.distal.com) Authentication-Results: mx1.freebsd.org; none dkim-signature: v=1; a=rsa-sha256; d=relay.distal.com; s=mail; c=relaxed/relaxed; q=dns/txt; h=From:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type:Content-Transfer-Encoding:In-Reply-To:References; bh=SSSjp6vX+XiwitDVSJEzvz1p5969mkVVWN3xrCUasEc=; b=rPF7DiCKKf+ppPfyMMYQ8Efq6TwGcapHCuCug6xeSP47ZCwctCyQXLEgDmSVKjYkx5r85Qombx5NMsJSZPm9GKoRa18ayzwvBAXz6TSKYgYQSS3C5FGq+nb1c3PGhpWBN/xUqzqxj0dC56mXuop8bDPUAlTD2cPyaUzYgUMQYDTMLi7D4+20x56wy6UrSWJEcIl8tdKCT6pQh+Etrhyov3owDVSUPF6ODTFjki23Kan0eQRSlMvQYi34PG WYS/eLmlOMItqyQhf3Ph9VEYRDjDiWw0LgXiJ4WHUmK8dHgOUPz2oO1FTfX6Jm35SqMfousmSPH7a4/d1dHKvebHBiQg== Received: from mail.distal.com (pool-108-45-29-236.washdc.fios.verizon.net [108.45.29.236]) by relay.wiredblade.com with ESMTPSA (version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256) ; Mon, 6 Oct 2025 17:12:32 +0000 Received: from smtpclient.apple ( [2600:4040:2cc8:f620:f141:7f06:f21:8921]) by tristain.distal.com (OpenSMTPD) with ESMTPSA id fc9bde79 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Mon, 6 Oct 2025 13:12:30 -0400 (EDT) Content-Type: text/plain; charset=utf-8 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 (Mac OS X Mail 16.0 \(3864.100.1.1.5\)) Subject: Re: Network interface renaming From: Chris Ross In-Reply-To: Date: Mon, 6 Oct 2025 13:11:44 -0400 Cc: freebsd-net@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <60FE3378-C634-4E6F-80B2-7E9373EA719A@distal.com> References: <1CB5332A-5E7E-420A-A6AC-3F2D70A0B6C3@distal.com> To: Lexi Winter , =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= X-Mailer: Apple Mail (2.3864.100.1.1.5) X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[freebsd]; ASN(0.00)[asn:3842, ipnet:168.235.104.0/22, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4cgQnM2b19z3spd > On Oct 5, 2025, at 23:40, Lexi Winter wrote: >=20 > Chris Ross wrote in <1CB5332A-5E7E-420A-A6AC-3F2D70A0B6C3@distal.com>: >> 1. Is interface renaming just too dangerous to use? >=20 > i use interface renaming on many systems and have not run into = problems > with it. however, i don't use local_unbound, and also don't tend to > rename external or vlan interfaces. Yeah, I think it=E2=80=99s the vlan interfaces that are the issue. You = mention that interface renaming happens very early (before the interface is brought up), but this is clearly not the case for me. I can see the interfaces = being renamed after the dhclient starts on the primary outside interface. So probably still somewhere in netif, but interestingly I see after the renames a =E2=80=9CStarting Network: lo0 ix0=E2=80=9D. Note, not = including any of my vlan interfaces. And, it looks like my local_unbound problem is not related to = interfaces. I took a video of the boot process, and saw the errors there. > in /etc/syslog.conf, there is a commented example of using syslogd to > write boot messages to /var/log/console.log. i suggest enabling this, > which will make it easier to see where things are failing. Ahh, that=E2=80=99s helpful, thank you. I=E2=80=99ve turned that on. = It=E2=80=99s not quite as good as watching the console, for example the output of interface renaming is much more in the kernel messages than the single word output to console, but. It gives me most things and I=E2=80=99ll enjoy = keeping that. > On Oct 6, 2025, at 05:46, Dag-Erling Sm=C3=B8rgrav = wrote: >=20 > Chris Ross writes: >> 1. Is interface renaming just too dangerous to use? >=20 > Yes. For instance, `service netif stop` and `service netif restart` = may > not work properly, packet filter rulesets may fail to load, etc. :-) Clearly multiple opinions on this, thank you for yours. I worry = about the same. > Anything that failed to start will presumably have left error messages > in /var/log/messages. Sadly not. There was no information about the local_unbound failure in any logs, until adding the console.log discussed above. messages has a few lines upon _sucessful_ startup, and daemon.log does as well. But, I have it now. It=E2=80=99s an IPv6 error: Oct 6 11:55:35 logrus kernel: [1759766134] local-unbound[78949:0] = error: can't bind socket: Can't assign requested address for = 2600:4040:2cc8:f600::1 port 53 Oct 6 11:55:35 logrus kernel: [1759766134] local-unbound[78949:0] fatal = error: could not open ports I=E2=80=99m not sure how to prevent this, since these addresses were = just assigned moments earlier by dhcpcd, and I don=E2=80=99t know why a port can=E2=80=99t be opened. I=E2=80=99m in the midst of working out other = issues with dhcpcd start-up though, so this could all change. I=E2=80=99ll consider = this local_unbound start-up problem to be a consequence of that issue, and not currently and issue in and of itself. Thanks all. - Chris=