Arch Linux

BrianDMS

Member

From: Amsterdam, Netherlands

Registered: 2022-03-10

Posts: 25

Network stack choice - networkd vs iwd built-in

Hey, I'm making a new setup for a dev workstation laptop, trying sth different than NM+wpa_supplicant this time to learn new things.
I'm wondering if you guys have any opinions about systemd-networkd as well as iwd's built-in network configuration, as I'm debating between those two.

The setups I'm considering are:
- systemd-networkd + systemd-resolved (for dns resolution) + iwd (wireless daemon only)
- iwd (network configuration and wireless daemon) + systemd-resolved (for dns resolution)

In case of systemd-networkd, it needs 1/2 configs to enable DHCP for wireless/wired network interfaces. In case of iwd, it also needs 1 config file to enable build-in network configuration if i want to use it. Systemd-resolved needs that 1 symlink to use stub mode regardless, if i understand everything correctly.

So both setups are reasonably simple to configure, and I know they're both working fine, but I'm wondering what will be a better choice for a desktop-focused laptop running a wayland wm/compositor. Especially with regard to ease of use, stuff like connecting to networks like eduroam, perhaps applet/widget support in waybar, wofi or whatever. Or perhaps it's better to consider netctl or stick with NM instead? I've read through a ton of wiki pages but I can't rly judge what's better/simpler for desktop usecase (considering I won't be using any opinionated DE's that enforce their own network stack in any way).

Last edited by BrianDMS (2023-09-02 10:49:25)

---

alias ffs='sudo $(fc -ln -1)'

twelveeighty

Member

Registered: 2011-09-04

Posts: 1,452

Re: Network stack choice - networkd vs iwd built-in

The standard Arch answer will always be: try both and decide for yourself which one you like best. Recommendation topics usually end up in "Topics Going Nowhere", because the answers/choices get outdated very quickly. My personal choice would be NM, since it 'just works' (tm) for all my use-cases; I do not run a DE.

BrianDMS

Member

From: Amsterdam, Netherlands

Registered: 2022-03-10

Posts: 25

Re: Network stack choice - networkd vs iwd built-in

I did try both and both work basically just as well at least right now, but I don't have any experience with any of them, I don't know of any edge cases, weird behaviors, compatibility, everything that would make one actually prefer one over another. Though I guess switching between them is literally just changing 1 config and enabling/disabling 1 service so it's not like I really have to be worrying about this I guess tbh... Sry for using the wrong board, wasn't quite sure where to ask stuff like this

---

alias ffs='sudo $(fc -ln -1)'

cloverskull

Member

Registered: 2018-09-30

Posts: 277

Re: Network stack choice - networkd vs iwd built-in

I use systemd-resolved and out of your questions can only speak to that. Setup and configuration was straightforward, DNSSEC and DNS over TLS both work well. I've had problems with "captive" internet (i.e., signing in at a hotel) and also doing any kind of gpg keyserver attempts. So, not sure what that's about, it would be cool to have an easy switch on/off for systemd-resolved and whatever NetworkManager uses for DNS resolution

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,103

Re: Network stack choice - networkd vs iwd built-in

https://wiki.archlinux.org/title/Networ … d-resolved

systemd-resolved will be used automatically if /etc/resolv.conf is a symlink to /run/systemd/resolve/stub-resolv.conf, /run/systemd/resolve/resolv.conf or /usr/lib/systemd/resolv.conf.

The hotels DNS perhaps would intercept your query and redirect you to the LAN host w/ the captive portal what got spoiled by the resolved cache,  opening some never before used domain would have forced a full resolution and if you properly got a DNS from the hotels dhcp and that set has resolved's main DNS you would have gotten the captive portal (but that's all speculation)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,643

Re: Network stack choice - networkd vs iwd built-in

Sry for using the wrong board, wasn't quite sure where to ask stuff like this

A couple comments.  First, Newbie corner was a good choice.  In any event, you cannot open a topic in "Topics Going Nowhere".  Moderators move things there,  and it is generally not punitive.  We use it as a place for conversations we don't want the major search engines or Bing to index.  We use it for product recommendations because we don't choose to endorse commercial products, and because recommendations go stale so fast in the world of Linux.

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way