systemd-networkd
Network daemon in Networking & smart home
People recommend systemd-networkd for its simple configuration and tight integration with systemd-resolved. Critics say it clashes with NetworkManager on some distros and is opaque to debug.
11 people recommended systemd-networkd in Hacker News comments and 6 criticized it, November 2025 to October 2026.
Summary written by Claude from 20 comments. It was written before the November 2026 recount, and 19 of those comments still count.
17 people gave an opinion
- recommend it
- 11
- mixed feelings
- 0
- warn against or regret it
- 6
The record
Recommended in 7 of 12 months
In 9 different threads.
- November 2025: recommended
- December 2025: recommended
- January 2026: recommended
- February 2026: not recommended
- March 2026: not recommended
- April 2026: recommended
- May 2026: recommended
- June 2026: not recommended
- July 2026: recommended
- August 2026: not recommended
- September 2026: recommended
- October 2026: not recommended
Why it doesn’t carry the badge
- 11 people recommend itNeeds 10 or more, met.
- 1.8 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 7 of 12 monthsNeeds 4 or more, met.
- Recommended in 9 threadsNeeds 5 or more, met.
- The biggest thread supplies 27% of its recommendersNeeds half or less, met.
The same rules apply to every product, and the badge can’t be bought. Mixed feelings count toward neither side. How the badge works
What people say about it
Reasons grouped from a sample of 19 of the 19 opinions about it, picked in proportion to how many people recommend it, have mixed feelings and criticize it. Each mark is one comment in the sample. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Integrates well with systemd-resolved
“I'm glad systemd-networkd (advertising) and systemd-resolved (finding) just integrate these concerns for me”
Comment from 19 Sep 2026 in “Systemd is a suite of basic building blocks” “systemd-networkd and systemd-resolved do some mutual coordination stuff that's pretty nice”
Comment from 23 Dec 2025 in “Snitch – A friendlier ss/netstat” “I'm quite happy with systemd-resolved and systemd-networkd”
Comment from 12 May 2026 in “A Caddy Cert Expired Because Systemd-Resolved Was Selectively Broken” - Comment from 12 May 2026 in “A Caddy Cert Expired Because Systemd-Resolved Was Selectively Broken”
Handles DHCP leases and hostnames
“now implements a resolve hook for its internal DHCP server, so that the hostnames tracked in DHCP leases can be resolved locally”
Comment from 18 Dec 2025 in “Systemd v259” “It has been sufficient to add the couple dozen static allocations to the configuration files and forget DHCP exists.”
Comment from 4 Dec 2025 in “Kea DHCP: Modern, open source DHCPv4 and DHCPv6 server” Useful on servers and small boards
“We are running systemd with all bells and whistles on Raspberry Pi based 1 GB RAM systems.”
Comment from 3 Nov 2025 in “X.org Security Advisory: multiple security issues X.Org X server and Xwayland” “very well documented/organised. I find it pretty useful on servers.”
Comment from 12 May 2026 in “A Caddy Cert Expired Because Systemd-Resolved Was Selectively Broken” Stable and low maintenance
“I've had the same stable prefix for over a year now, using systemd-networkd”
Comment from 24 Apr 2026 in “IPv6 Traffic Crosses the 50% Mark for the First Time”
What people warn about
Each mark is one comment
Clashes with NetworkManager on some distros
“I have often have to fight between system-networkd and NetworkManager on some distros”
Comment from 19 Dec 2025 in “Systemd v259” “I consider NetworkManager bad and systemd-networkd worse”
Comment from 12 May 2026 in “A Caddy Cert Expired Because Systemd-Resolved Was Selectively Broken” Missing some DHCP features
“is no longer supported by systemd-networkd (because they are puritans”
Comment from 4 Dec 2025 in “Kea DHCP: Modern, open source DHCPv4 and DHCPv6 server” “systemd-networkd not handling real world DHCP fields”
Comment from 1 Dec 2025 in “A Love Letter to FreeBSD” Dismissed along with other systemd parts
“not use systemd-networkd or systemd-timesyncd either”
Comment from 12 May 2026 in “A Caddy Cert Expired Because Systemd-Resolved Was Selectively Broken”
What people said
All 19 opinions about it, newest first. Each links to the original comment.
“I'm glad systemd-networkd (advertising) and systemd-resolved (finding) just integrate these concerns for me”
“One of my own gripes is speed for quite a few basic procedures in networkd.”
“I rather like systemd-networkd over the other four or five ways of managing the network”
“systemd-networkd in a restart loop continuously consuming 100% CPU”
“move to full systemd-resolved / networkd”
“very well documented/organised. I find it pretty useful on servers.”
“I consider NetworkManager bad and systemd-networkd worse”
“I'm quite happy with systemd-resolved and systemd-networkd”
“not use systemd-networkd or systemd-timesyncd either”
“I've had the same stable prefix for over a year now, using systemd-networkd”
“I have no clue what Lovecraftian horrors systemd-networkd generates”
“Can be done easily with systemd-networkd, because you can match .network file configurations on SSID.”
“systemd-networkd and systemd-resolved do some mutual coordination stuff that's pretty nice”
“I have often have to fight between system-networkd and NetworkManager on some distros”
“now implements a resolve hook for its internal DHCP server, so that the hostnames tracked in DHCP leases can be resolved locally”
“is no longer supported by systemd-networkd (because they are puritans”
“It has been sufficient to add the couple dozen static allocations to the configuration files and forget DHCP exists.”
“systemd-networkd not handling real world DHCP fields”
“We are running systemd with all bells and whistles on Raspberry Pi based 1 GB RAM systems.”
Counts come from 1,791,911 Hacker News comments labeled by Claude, November 2025 to October 2026, with data through October 31, 2026. Counts updated 2 Nov 2026. How we count. Report a mistake.