You are not logged in.
In a recent conversation on #archlinux, I found this reponse to !netctl:
avoid it. it's cumbersome and does a worse job than the underlying tools themselves will do when used directly (eg. with roaming). please consider systemd-networkd, NetworkManager, connman, or other tools
For a headless server, I feel silly using network "tools" rather than just plopping an IP in a configuration somewhere and being done with it, and systemd-networkd doesn't exist in the mirrors or the AUR.
In looking around a bit, I found this entry in the Wiki, but is it really appropriate expect to create a new, untracked file for managing static IPs? It really seems like there should be a "standardized" way to assign static IPs without having to write scripts for it. Are we in a transitional period until systemd-networkd gets written or something?
Last edited by synthead (2014-02-23 02:41:35)
Offline
systemd-networkd is a new feature of systemd 209. It should be a great answer for what you're needing, but it's only in the [testing] repo right now.
At this point, the service file in the wiki you linked to is probably the best option.
Online
systemd-networkd is a new feature of systemd 209. It should be a great answer for what you're needing, but it's only in the [testing] repo right now.
At this point, the service file in the wiki you linked to is probably the best option.
Oh great! That's exciting. I'll anticipate systemd-networkd for networking in the near future, thanks!
Offline