Chris, Here is an important caveat.... to override a system-supplied file in /usr/lib/systemd/network in a permanent manner (i.e even after upgrade), place a file with same name in /etc/systemd/network and symlink it to /dev/null This is somethign you have to be careful about in Archlinux.... the etc/systemd/... files take precedence but in this case these files would be in the mix since they do not exist in /etc/systemd/network. Here is a link to the latest info. See the changelog news at the beginning! https://wiki.archlinux.org/index.php/systemd-networkd Networkd developers blog - https://coreos.com/blog/intro-to-systemd-networkd/ More blogs..... http://beaveris.me/systemd-networkd-with-roaming/ My network - [root@alarmpi network]# wpa_supplicant -B -i wlan0 -D wext -c /etc/wpa_supplicant/wpa_supplicant-wlan0.conf Successfully initialized wpa_supplicant [root@alarmpi network]# networkctl list IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 ifb0 ether off unmanaged 3 ifb1 ether off unmanaged 4 eth0 ether routable configured 5 wlan0 wlan no-carrier configuring 5 links listed. [root@alarmpi network]# dhcpcd wlan0 dhcpcd[1771]: version 6.7.1 starting dhcpcd[1771]: DUID 00:01:00:01:1c:9a:54:1a:02:05:07:c5:cf:fb dhcpcd[1771]: wlan0: IAID 7b:85:f2:6e dhcpcd[1771]: wlan0: soliciting an IPv6 router dhcpcd[1771]: wlan0: rebinding lease of 192.168.0.202 dhcpcd[1771]: wlan0: leased 192.168.0.202 for 86400 seconds dhcpcd[1771]: wlan0: adding route to 192.168.0.0/24 dhcpcd[1771]: wlan0: adding default route via 192.168.0.9 dhcpcd[1771]: forked to background, child pid 1815 [root@alarmpi network]# [root@alarmpi network]# networkctl list IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 ifb0 ether off unmanaged 3 ifb1 ether off unmanaged 4 eth0 ether routable configured 5 wlan0 wlan routable configured 5 links listed. [root@alarmpi network]# 73 Doug WA3DSP http://www.crompton.com/hamradio