On 15/3/23 01:53, David Wright wrote:
systemd-networkd is definitely the cleanest way to go. Hence I also use it on all my systemsI had hoped (not very hopefully) the solution wouldn't involve bashing kernel parameters. From previous journeys in this area systemd-networkd does a much neater job and has huge numbers of options. This is my worstation configI hope it gets better :)root@client:/etc/systemd/network# cat wired_lan.network [Match] Name=enp7s0 [Network] DHCP=yes Address=10.31.40.68/24 Gateway=10.31.40.1 DNS=10.31.40.4 10.31.40.5 Address=2403:5800:c101:b700:beef::44/64 IPv6PrivacyExtensions=yes IPv6AcceptRA=yes Domains=lan example.com [IPv6AcceptRA]Any reason for running ifupdown in preference to systemd-networkd on the enp0s3 machine? All mine run the latter, hence being rusty on the contents of /e/n/i.
I am only looking at ifup/down as that is the default in bookworm for a non-graphical install.
I did a bit of experimentation with the installer and you don't get any options during the install to select networking method. You either get NetworkManager if you do a graphical install or ifup ifdown non graphical.
I looked at the if-up code in /etc/network/if-up.d/resolved #!/bin/sh # # Script fragment to make ifupdown supply DNS information to resolved #I did an graphical install as a test and NetworkManager.service communicates to systemd-resolved by the internal message bus and I saw dhcp provided DNS being passed and used by systemd-resolved
Reading the documentation, systemd-resolved is tightly integrated with systemd-networkd as resolved reads all the systemd-networkd configuration files. The reverse may not be so true.
The situation now appears to be that networking.service (ifup/ifdown), NetworkManager.service, systemd-networkd.service all work (or can work) with systemd-resolved
systemd-networkd *should* be able to update systemd-resolved with DNS from DHCP but I haven't seen evidence it does so far
-- Jeremy (Lists)