From nobody Mon Oct 6 03:40:39 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 4cg4mc0v8cz69WC0 for ; Mon, 06 Oct 2025 03:40:48 +0000 (UTC) (envelope-from ivy@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R13" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4cg4mb4vgvz43NV; Mon, 06 Oct 2025 03:40:47 +0000 (UTC) (envelope-from ivy@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1759722047; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=lRQaCPXXFR8ofdZn8D9BOdPKbcBNMnL0+IpsGzhTMwM=; b=so3pWB71gmbATb3NKKXqkDMxICLyeV7LBYKQoS13qTJyQbuUS1qKfjjCpmolyrPR+Md5HC uovnwEju0TpYpfRrL6lNCihCQg6IX77wgHFblDX6WjCX4HlEPGvj/m0gciy54DY93uqxRr DMlz0qh7v7ZT+WfJIqRqGSm9qoTegTweM7i+dHANTWBXxawZWO6jSBkKPrXumIxljXwU5z TpLHxDPLPTVD/vv0rK6teKGvLko3CNzF8x2tnNlOIna7qfbgT+xkVlzp8Td3NgDsXMj2VA GmxCZXqa9iCZ05aevd3iKh2qlumfQfL4tOJjPuYBan+GeIrNhNcLJcVckvXABA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1759722047; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=lRQaCPXXFR8ofdZn8D9BOdPKbcBNMnL0+IpsGzhTMwM=; b=MEPYyf5RDP4dj+LXZSDrigkNFDajcUpNekmgpNjcv7zlDJ38cBxjejxXH3lD1A9F+Eu+Ck 2C9f1fzZeEBPbe+XCNG+X2yi1Cf28jVvsAcLnijDgUlRYJRDNB9iVA8gNgvwWRJOxM6IzX CYsJj5oYdbi3AHPUM9cOlRi6zficdLCFz8rrWefFlOzN04HpaIrPwm8ZEjOmBeqwMTJ+cE 69VcmnDL2X2lZozz3BcucJwthuT/Tju7Avhx1I/bsKIAbZZckzVaFreiuhZUXWb8rBQUHc 4vgZe6D4LLLyybYnM7hYnFmojQLAldBKbz1R45ja0ZUpVb9YKotfM1KVgxA0Pg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1759722047; a=rsa-sha256; cv=none; b=cHmyDwqujiy7MC5c0tGMP4L11wWUcdC4mDm5excZdTpuFWOyHUaCtLYAQgwvg7CSbBDZM9 mtx5gcEbTixKrUkBU7V8ft9dJcqpybh+Dipii8PQNcjuNmok1zhfa7HWc0C23MM3kqZ6AF 6uJLvjkxAtR95LYp3mEJz9+33IFjjkG3kgzY/bb3Qjr6CxYeQ8pJxj0SYoV62qHt9sE8nt p6mNeVS4JnIX6ZQZK9HA9+TUlb/SoXO2SavsJXbYxvmBuMypQZsswRb/GLR8s2vDqr37ez xCkykmmvx6HzpHt9ROtpUyPPAZ5RaKlHOb7izi905kt89Zx2iE7pbz3DRnEfHg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from amaryllis.le-fay.org (amaryllis.le-fay.org [IPv6:2a00:1098:6b:400::9]) (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) (Authenticated sender: ivy/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4cg4mZ70m5zNDR; Mon, 06 Oct 2025 03:40:46 +0000 (UTC) (envelope-from ivy@freebsd.org) Date: Mon, 6 Oct 2025 04:40:39 +0100 From: Lexi Winter To: Chris Ross Cc: freebsd-net@freebsd.org Subject: Re: Network interface renaming Message-ID: Mail-Followup-To: Chris Ross , freebsd-net@freebsd.org References: <1CB5332A-5E7E-420A-A6AC-3F2D70A0B6C3@distal.com> 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: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="dX4+tuP1G26n5KIT" Content-Disposition: inline In-Reply-To: <1CB5332A-5E7E-420A-A6AC-3F2D70A0B6C3@distal.com> --dX4+tuP1G26n5KIT Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Chris Ross wrote in <1CB5332A-5E7E-420A-A6AC-3F2D70A0B6C3@distal.com>: > 1. Is interface renaming just too dangerous to use? 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. > 3. Can I verify when local-onbound, or other, daemons are starting > up and if they=E2=80=99re failing get that reported somewhere I can see > After the system is multi-user? 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. interface renaming happens very early (before the interface is brought up) so it usually shouldn't cause any problems, but the output from the local_unbound startup script would make it easier to see what's going on. --dX4+tuP1G26n5KIT Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQSyjTg96lp3RifySyn1nT63mIK/YAUCaOM6MwAKCRD1nT63mIK/ YFnpAQDu6l0Sr5e2pOYZxNRevS148tEMLRmJIlWoq/p15VGmkQEAyca7SdepLGfD MT0fFbGt+7mnCfq00WkBdjDLmLfD0Ag= =h+ir -----END PGP SIGNATURE----- --dX4+tuP1G26n5KIT--