I'm trying to understand a little more about the difference between Raspi OS Bookworm's networking software and that used by Ubuntu 24.04, both as set up on the "average" up-to-date Raspberry Pi 5.
Let me start by saying I used not to be a fan of NetworkManager, but with a little more familiarity, and particularly my recent experience using it with Ubuntu 24.04 on the Pi 5, the more I've begun to regard it as friend rather than foe. Even though it is not a complete piece of software in its own right, and is really just managing a collection of various other software packages, with the right choice of software and some sane configuration, it really does seem to offer a flexible solution to someone who is constantly developing different IOT projects (often ESP32-based) and testing them for network compatibility with the Pi and a selection of PC systems (Linux and Windows).
So I've abandoned experimenting with system.networkd for the time being (because it often seems it's a choice between systemd.networkd and NetworkManager.
As far as I can gather, the following network packages are used in the above cases:
Ubuntu 24.04 (as installed by RPI Imager):
NetworkManager (coordinating application)
ModemManager (service)
usb_modeswitch (application)
wpa_supplicant (service)
iproute2 (application)
avahi (service)
systemd.resolved (service for DNS)
Raspi OS Bookworm (as installed by RPI Imager):
NetworkManager (coordinating application)
ModemManager (service)
usb_modeswitch (application)
wpa_supplicant (service)
ifupdown <-- present, but considered legacy (i.e. we're not resorting to config via /etc/network/interfaces)
iproute2 (application)
avahi (service)
Question: since Raspi OS Bookworm (as standard) doesn't use systemd.resolved, what does it use instead for DNS?
Let me start by saying I used not to be a fan of NetworkManager, but with a little more familiarity, and particularly my recent experience using it with Ubuntu 24.04 on the Pi 5, the more I've begun to regard it as friend rather than foe. Even though it is not a complete piece of software in its own right, and is really just managing a collection of various other software packages, with the right choice of software and some sane configuration, it really does seem to offer a flexible solution to someone who is constantly developing different IOT projects (often ESP32-based) and testing them for network compatibility with the Pi and a selection of PC systems (Linux and Windows).
So I've abandoned experimenting with system.networkd for the time being (because it often seems it's a choice between systemd.networkd and NetworkManager.
As far as I can gather, the following network packages are used in the above cases:
Ubuntu 24.04 (as installed by RPI Imager):
NetworkManager (coordinating application)
ModemManager (service)
usb_modeswitch (application)
wpa_supplicant (service)
iproute2 (application)
avahi (service)
systemd.resolved (service for DNS)
Raspi OS Bookworm (as installed by RPI Imager):
NetworkManager (coordinating application)
ModemManager (service)
usb_modeswitch (application)
wpa_supplicant (service)
ifupdown <-- present, but considered legacy (i.e. we're not resorting to config via /etc/network/interfaces)
iproute2 (application)
avahi (service)
Question: since Raspi OS Bookworm (as standard) doesn't use systemd.resolved, what does it use instead for DNS?
Statistics: Posted by tfrond — Thu Oct 17, 2024 2:37 am