Strongswan after network-online instead of network

The systemd service file shipped with strongswan has strongswan started after `network-online`. It turns out that this is for good reason: failure to connect on boot otherwise. See this thread on the mailing list, which my colleague initiated after finding that our NixOS strongswan config wouldn't connect on boot: https://lists.strongswan.org/pipermail/users/2017-January/010359.html Tested on a local config (which has the strongswan service config overridden).
NixOS · Jul 17, 2017 · b09d036 · b09d036
1 parent c4783a9
commit b09d036
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/nixos/modules/services/networking/strongswan.nix b/nixos/modules/services/networking/strongswan.nix
@@ -120,7 +120,7 @@ in
       wantedBy = [ "multi-user.target" ];
       path = with pkgs; [ kmod iproute iptables utillinux ]; # XXX Linux
       wants = [ "keys.target" ];
-      after = [ "network.target" "keys.target" ];
+      after = [ "network-online.target" "keys.target" ];
       environment = {
         STRONGSWAN_CONF = strongswanConf { inherit setup connections ca secrets; };
       };