Date: Mon, 06 Oct 2025 11:46:12 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org> To: Chris Ross <cross+freebsd@distal.com> Cc: freebsd-net@freebsd.org Subject: Re: Network interface renaming Message-ID: <865xcs8isb.fsf@ltc.des.dev> In-Reply-To: <1CB5332A-5E7E-420A-A6AC-3F2D70A0B6C3@distal.com> (Chris Ross's message of "Sun, 5 Oct 2025 23:11:43 -0400") References: <1CB5332A-5E7E-420A-A6AC-3F2D70A0B6C3@distal.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Chris Ross <cross+freebsd@distal.com> writes:
> 1. Is interface renaming just too dangerous to use?
Yes. For instance, `service netif stop` and `service netif restart` may
not work properly, packet filter rulesets may fail to load, etc.
> 2. Is there any way I can make the interfaces take
> their names earlier?
> 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?
To see the order they start in:
rcorder /etc/rc.d/* /usr/local/etc/rc.d/*
Anything that failed to start will presumably have left error messages
in /var/log/messages.
DES
--
Dag-Erling Smørgrav - des@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?865xcs8isb.fsf>