You are not logged in.
This is a little strange, especially since I can't really find anything about this on the 'net. I manage several network interfaces with systemd-networkd, and after a pacman -Syu, none of my interfaces will come up using the systemd-networkd service. I have [Match] and [Network] sections in .network files in /etc/systemd/network; nothing changed there. No .pacnew files that are relevant to this not working. dmesg doesn't report anything funky.
The closest thing to an error message I found is seeing Status: "Processing requests..." when running systemctl status systemd-networkd (although it is still reported as "active").
What should I check?
Offline
Also, I have my network interfaces set to a permanent names via udev rules, if it matters.
Offline
Offline
The network interfaces are actually down, though. They don't have IPs. Starting the systemd-resolved service doesn't do anything as far as bringing up the interfaces, unfortunately.
Last edited by synthead (2014-06-04 07:06:20)
Offline
Interesting... downgrading to systemd-212-3 fixes the issue. Suppose I should file a bug at this point.
Offline
Offline
The closest thing to an error message I found is seeing Status: "Processing requests..." when running systemctl status systemd-networkd (although it is still reported as "active").
What should I check?
I think that is normal - systemd-networkd is showing the same status for me and my .network file is working.
Looking at your bug, the major difference is that my .network matches on Name, not MACAddress (I use .link files to map MACAddress to a persistent name rather than an explicit udev rule)
Offline
Yeah, MAC address matching seems to be the poblem. falconindy reposted the bug to systemd's bug tracker: https://bugs.freedesktop.org/show_bug.cgi?id=79638
Offline