Thus in the /etc/systemd/network directory was created the static.network file with its respective settings.
Now the reason of this post. In both links are covered about
How to define DHCP and Static IPs
but is indicated the following in the second link:
Next enable systemd-networkd. You donât need to start the service yet because your old network is still running and there is currently no systemd-networkd defined.
systemctl enable systemd-networkd
If is executed the systemctl list-units | grep network command appears the following:
networking.service load active exited Raise Network interfaces
network.target load active active Network
And for the systemctl list-unit-files | grep network command appears the following:
I dont understand enough of this to be sure, but I would ask you to note that only one networking daemon should be enabled at any time.
Yes correct, just to sharp the idea remember
Therefore if to define DHCP and Static IPs is mandatory work with systemd-networkd
Why from the beginning is disabled the systemd-networkd service?
In other words the official docs works with systemd-networkd but the current daemon is networking.service. Is it other different than the systemd world, right?
You are learning that systemd is overly complicated.
Practice and practice ⊠it has its own âtricksâ
Consider using a non-systemd distro (preferably dinit) ⊠it will make your config work simpler.
I dont know networking.service, but its name sounds like it is part of systemd too.?.. are you sure it is a daemon?
⊠ie if you look with âps axâ is it running?.. or is it just some name for a service and not a real daemon.
Systemd seems to name all sorts of abstract things , that dont exist or run as a program⊠it is hard to know what they are. Dont let them confuse you⊠find out what the real daemon process is⊠that is the only thing that matters.
Other init systems do not use these mysterious abstract entities. There are daemon processes that are either running or not running, and that is all there is.
Probably 'cause your system is not using it? Maybe NetworkManager?
It sounds like you donât know enough about whatâs going on - donât touch it - the installer defaults are usually okay for most people and smart enough. I hardly ever have to tweak my network configuration - it mostly just works from the moment of install (I mostly use DHCP - but - e.g. on my desktop machine with Pop!_OS 22.04 - I run my Synergy KVM âserverâ - so it needs a fixed IP address - so I set it in the Gnome Settings âNetworkâ applet - but - its also outside the DHCP scope of my router, and regardless, I have a static lease set for that IP address in my router, regardless).
Pop!_OS 22.04 system (x86_64 on a ThinkPad E495) :
Note: it says its disabled - but itâs still running (âactive (running)â) - donât ask me to explain why, I donât know and I donât care enough to find the answer.
If I look at my network settings on the Pi5 (Ubuntu 24.04) :
ââx@razuberi ~
â°â†nmcli -p device 2 â”
=====================
Status of devices
=====================
DEVICE TYPE STATE CONNECTION
------------------------------------------------------------------------------------
eth0 ethernet connected netplan-eth0
wlan0 wifi connected REDACTED
lo loopback connected (externally) lo
p2p-dev-wlan0 wifi-p2p disconnected
This shows that the NetworkManager config is coming via netplan (ânetplan-eth0â)
My other Ubuntu 24.04 (a Dell Latitude 7270) isnât running systemd-networkd :
Itâs âloadedâ but inactive⊠So itâs not really runningâŠ
All the above are working just fine for me - I donât need to fiddle with anything thereâŠ
My Debian 9 uses dhcpcd, Debian 11 and 12 are using NetworkManager, Ubuntu 24.04 x64 is using netplan / NetworkManager (renderer: NetworkManager), Pop!_OS is using NetworkManagerâŠ
Note : there is no systemd unit file for systemd-networkd on my RHEL9 VM - so itâs purely running NetworkManager and using NetworkManager aloneâŠ
So this begs the question - WHY do you think you need to fiddle with this stuff? Donât mean to sound rude - but Iâm curious what youâre hoping to achieveâŠ
but its name sounds like it is part of systemd too.?.. are you sure it is a daemon?
Being honest I always assumed everything shown through the systemctl command and having .service in its Unit Name was a daemon.
⊠ie if you look with âps axâ is it running?.
It does not appear
or is it just some name for a service and not a real daemon.
Oh that sentence ⊠it changes now my perspective about services and daemon ⊠well more to learn through research
Systemd seems to name all sorts of abstract things , that dont exist or run as a program⊠it is hard to know what they are. Dont let them confuse you⊠find out what the real daemon process is⊠that is the only thing that matters.
Thank you .. thatâs why I use the systemctl cat <unitname> too for more details
Other init systems do not use these mysterious abstract entities. There are daemon processes that are either running or not running, and that is all there is.
Oh âŠ
Dan
Probably 'cause your system is not using it? Maybe NetworkManager?
I thought the same, but in other machines where Debian 12 as server was installed and NetworkManager never was installed the output is the same is reported in the OP
Yes, I know I indicated in other post that NetworkManager was installed in Debian 12 server, it is true. It was in other machine and the fact NetworkManager was already uninstalled because was not possible integrate in peace NetworkManager in Debian. Thus to solve the situation of the static IP address I found the 2 links shared
It sounds like you donât know enough about whatâs going on - donât touch it - the installer defaults are usually okay for most people and smart enough.
Yes, I am agree, but because I am working with VirtualBox, the Debian instances are in isolated environments. Thus if something goes wrong is ok.
I hardly ever have to tweak my network configuration - it mostly just works from the moment of install (I mostly use DHCP - but - e.g. on my desktop machine with Pop!_OS 22.04 - I run my Synergy KVM âserverâ - so it needs a fixed IP address - so I set it in the Gnome Settings âNetworkâ applet - but - its also outside the DHCP scope of my router, and regardless, I have a static lease set for that IP address in my router, regardless ).
I always work with static ips in my Lan for SSH and network access ⊠and well to work with Web Applications with Spring. So I need the static ips. So far the goal was accomplished in peace for Fedora and Ubuntu. Now playing with Debian. It is part of the learning curve when anyone starts with a new distro. Letâs see what happens when I play with openSuSE too.
The nmcli command is not installed. Thus nothing involved about NetworkManager in this Debian 12 Server instance
My Debian 9 uses dhcpcd, Debian 11 and 12 are using NetworkManager, Ubuntu 24.04 x64 is using netplan / NetworkManager (renderer: NetworkManager ), Pop!_OS is using NetworkManagerâŠ
I tried the integration of NetworkManager in Debian 12 server was not possible. It is other history. Anyway the nmcli command would be installed only for referential report purposes . Anyway about Debian I found the 2 links shared in the OP and the syntax of the configuration file is not complicated as YAML. Thus I decided to work with the official approach of Debian.
Note : there is no systemd unit file for systemd-networkd on my RHEL9 VM - so itâs purely running NetworkManager and using NetworkManager aloneâŠ
It has a lot of sense because Fedora Server 41 works by default with NetworkManager too (nmcli)
So this begs the question - WHY do you think you need to fiddle with this stuff? Donât mean to sound rude - but Iâm curious what youâre hoping to achieveâŠ
No offense taken. Just to be clear:
Fedora : NetworkManager (nmcli command)
Ubuntu: Netplan (YAML)
Because I found more practical use the nmcli command:
For Ubuntu: I tried move from to YAML to the nmcli command. I remember in few places and even by you the key line: renderer: NetworkManager ⊠and other settings. Well it did not work as expected. It is other history
For Debian: I tried use NetworkManager and failed.
Thus for experimental purposes I tried to use these 3 OS in peace with the same approach of configuration NetworkManager.
For Ubuntu the reports of device and connections are not ok (there are no neither lo nor enp0s3) and even when is created a device and connection is impossible âupâ a connection. Almost the same situation with Debian for enp0s3. My unique assumption is that because each one was installed through VB the network settings would be the problem. Of course it is an assumption because it works fine for Fedora Server (installed through VB too)
Anyway I already have learned 3 ways to configure networks, it for each OS, and I did do a deep research of the systemctl and nmcli commands. So it is not a waste of time
disable the static ip for NM and use ifupdown for the static ip
use dhcpcd for everything
It depends which distro. Most distros setup something for a DHCP internet link at install time. I tend to leave that alone as it is separate from the LAN with static ipâs.
My modem is not on the LAN⊠it is separate and requires a separate ethernet or wireless interface.
Dont ask me why I configured it that way?
I think because I used to use the main machine as a gateway⊠it has 2 NICâs.
it changes now my perspective about services and daemon ⊠well more to learn through research 
