FS#40675 - systemd-networkd service in systemd-213-5 does not bring up any interfaces

Attached to Project: Arch Linux
Opened by Max Pray (synthead) - Wednesday, 04 June 2014, 07:43 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 04 June 2014, 14:33 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


In systemd-212-3, adding a .network file in /etc/systemd/network and starting the systemd-networkd service would configure and bring up an interface as expected. After upgrading to 213-5 without changing any configuration, the interfaces do not come up and are not assigned IPs.

Here are the contents of my .network files (they really aren't anything fancy):




I am aware that systemd-resolved is a new service that should be enabled for the systemd-handled resolv.conf located in /run, but the issue is not about resolving DNS. I experimented with starting and enabling systemd-resolved, but it has no effect on the interfaces.

Steps to reproduce:
1. Ensure that systemd-212-3 is installed.
2. Configure an interface in /etc/systemd/network via a .network file.
3. Run "systemctl enable systemd-networkd" as root.
4. Reboot and observe that the network connection is up and configured properly.
5. Upgrade to systemd-213-5.
6. Reboot and observe that no network devices are configured.
This task depends upon

Closed by  Dave Reisner (falconindy)
Wednesday, 04 June 2014, 14:33 GMT
Reason for closing:  Upstream
Additional comments about closing:  https://bugs.freedesktop.org/show_bug.cg i?id=79638
Comment by Randy McCaskill (rmccask) - Wednesday, 04 June 2014, 13:09 GMT
I have the same problem. It seems that eth0 is not being renamed to ens3 for me and since the network config is defined for ens3, it doesn't come up. I copied the ens3 network config to eth0 and can start the network on that device. That let me get online so that I could download a package for systemd-212-3. I have downgraded for now.
Comment by Dave Reisner (falconindy) - Wednesday, 04 June 2014, 13:12 GMT
Seems like a bug with MACAddress based matching. Not a packaging bug, please report this upstream.
Comment by Randy McCaskill (rmccask) - Wednesday, 04 June 2014, 13:41 GMT
I do not have any files in /etc/systemd/network and do not use MAC address matching. I do have a basic /etc/conf.d/network@ens3 which contains:
I noticed that when I was running the systemd-213-5, I didn't have the following line in my logs:
systemd-udevd[119]: renamed network interface eth0 to ens3
Comment by Dave Reisner (falconindy) - Wednesday, 04 June 2014, 13:42 GMT
That's not a file that systemd-networkd will ever read.... Typo?
Comment by Randy McCaskill (rmccask) - Wednesday, 04 June 2014, 13:54 GMT
I am doing what is defined here: https://wiki.archlinux.org/index.php/Network_configuration#Persistent_configuration_on_boot_using_systemd_and_udev_rules
It does claim that this is now deprecated but it is what I have been using and it was just marked as deprecated today after it broke.
Comment by Dave Reisner (falconindy) - Wednesday, 04 June 2014, 14:05 GMT
Ah, so you're just wasting my time. You aren't using networkd, and the bug report you're posting on isn't even relevant to your problem. If you use the native facilities that systemd provides for renaming, you'll find that things work as expected.
Comment by Randy McCaskill (rmccask) - Wednesday, 04 June 2014, 14:17 GMT
The updated version of systemd pulled in via pacman broke my networking. Reverting to the previous version of systemd restored it. I didn't say I was using networkd. I gave my information on this ticket since I thought it might be the same root problem. Maybe you think otherwise but there is no excuse for your attitude.