I bear no resemblance to an expert on networking, with absolutely none related to any part of NetworkManager other than removing it, but I have considerable experience in switching from traditional Debian ifupdown networking to systemd-network, dating back to Buster. Part of that is usingto see what is enabled or not, and using that as a guide to determine what to disable or remove. Other particulars I don't remember, but ifupdown and/or networking.service are either not enabled, or not installed. On the Bookworm booted now I have:In newer versions of systemd than Bookworm has, in some distros, systemd-network is a separate package.
Code:
systemctl list-unit-files | grep netCode:
# inxi -SSystem: Host: ara88 Kernel: 6.1.0-30-amd64 arch: x86_64 bits: 64 Desktop: TDE (Trinity) v: R14.1.3 Distro: Debian GNU/Linux 12 (bookworm)# dpkg-query -W | egrep 'netw|ifup|systemd'libpam-systemd:amd64 252.33-1~deb12u1libsystemd-shared:amd64 252.33-1~deb12u1libsystemd0:amd64 252.33-1~deb12u1systemd 252.33-1~deb12u1systemd-sysv 252.33-1~deb12u1systemd-timesyncd 252.33-1~deb12u1# systemctl list-unit-files | egrep 'net|ifup'dbus-org.freedesktop.network1.service alias -inetutils-inetd.service generated -systemd-network-generator.service disabled enabledsystemd-networkd-wait-online.service masked disabledsystemd-networkd-wait-online@.service disabled enabledsystemd-networkd.service enabled enabledsystemd-networkd.socket enabled enablednetwork-online.target static -network-pre.target static -network.target static -#Statistics: Posted by mrmazda — 2025-01-21 03:31 — Replies 1 — Views 50