On Tue, Mar 28, 2023 at 06:54:19PM +0200, Óscar García Amor wrote: > > Scanning the available docs, I found out that systemd-networkd > > is enabled by default. Could this be in conflict with netctl ? > > Yes, in fact, I advise you NOT to use netctl and to use systemd- > netword[1] directly. The reason for the netctl failure turned out to be that dhcpcd was not installed. Which was a bit of surprise, because netctl needs it. The reason for using netctl is that we want to maintain strict manual control. Anything that tries to be clever and connect automatically to whatever network is available, or that requires configuration to opt out of such functionality, is absolutely ruled out. I've been using netctl for ages, so that's what I know. Maybe systemd-networkd can do the same, but all my experience with how systemd services work confirms that they are designed to prefer convenience over security. And those two you can't have at the same time. A bit of history. There are actually two systems, both are used only for one specific very technical purpose. I installed them three years ago and sent them to the user. They both contain some specialised software that is considered a trade secret and highly confidential. So even if I advised the user to update those systems regularly, that was never done, after installation they were never again connected to any network. So imagine what happened when that special software needed an update. Nothing worked, trying to update the systems just failed and whatever we tried just got us deeper and deeper into a rabbit-hole. So we decided to re-install from scratch. The first one was done a month ago, now we are doing the second one. Kind regards, -- FA
