logoalt Hacker News

arcfour • today at 1:44 PM • 3 replies • view on HN

Why do you even need networkd for a router? Setting one up on Alpine (so not all this cruft) is easy as pie and the whole thing can cold boot in under 10 seconds... Would make the whole setup much more understandable + smaller attack surface...

> I usually prefer using systemd utilities wherever possible.

Ah. There's your problem. When something promises it can do anything and everything, rarely can it do much of it well, I find...

The type of issue you encountered is a pervasive failure mode you will encounter the more and more systemd utilities you rely on. For something like a router, systemd is wholly unnecessary. Try it! You'll agree.


Replies

o_-_o • today at 1:53 PM

Yeah this is why I have that Arch Linux uses systemd* by default. Will try Artix Linux[1]. "Artix Linux is a rolling-release distribution, based on Arch Linux. It uses real init systems, because PID1 must be simple, secure and stable."

[1] https://artixlinux.org/ [*] https://systemd-free.artixlinux.org/

hylaride • today at 3:19 PM

Networking is the biggest cause of issues I've had with systemd, mostly because of the systemd maintainer's insistence on strict adherence to modern RFC's to the detriment of legacy support. This has resulted in my having to deal with gross workarounds for various issues, including this 032 issue with multiple domains: https://docs.aws.amazon.com/linux/al2023/ug/deprecated-al2.h...

➕ show 2 replies
doublepg23 • today at 4:32 PM

> smaller attack surface

I literally run alpine in prod and home but I think the recent exploits in musl should give us pause if this is a fact or if it's a heuristic.