Date: Mon, 6 Oct 2025 04:40:39 +0100 From: Lexi Winter <ivy@freebsd.org> To: Chris Ross <cross+freebsd@distal.com> Cc: freebsd-net@freebsd.org Subject: Re: Network interface renaming Message-ID: <aOM6N1jI7lbIu9qW@amaryllis.le-fay.org> In-Reply-To: <1CB5332A-5E7E-420A-A6AC-3F2D70A0B6C3@distal.com> References: <1CB5332A-5E7E-420A-A6AC-3F2D70A0B6C3@distal.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] 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’re 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. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQSyjTg96lp3RifySyn1nT63mIK/YAUCaOM6MwAKCRD1nT63mIK/ YFnpAQDu6l0Sr5e2pOYZxNRevS148tEMLRmJIlWoq/p15VGmkQEAyca7SdepLGfD MT0fFbGt+7mnCfq00WkBdjDLmLfD0Ag= =h+ir -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aOM6N1jI7lbIu9qW>