Description:
Within netctl, users can run commands after the network connection is set up automatically by specifying them as "ExecPostUp". The problem is that the command run for "ExecPostUp" is executed before systemd's network.target is reached, which is an issue if the "ExecPostUp" command is something like "systemctl start $service", where $service requires network.target. This ultimately leads to an infinite loop of waiting, visible as netctl hanging forever when a profile is started.

Additional info:
Currently running netctl 1.7-1 from [core].


Steps to reproduce:
- Let $service be any systemd service which depends on network.target, and $profile be any netctl profile.
- Take down all network connections, and ensure $service is stopped.
- Put the line
ExecUpPost="systemctl start $service"
into /etc/netctl/$profile, and then use netctl to start that profile.

netctl then hangs, and you can use "systemctl list-jobs" to see that "netctl@$profile.service" is listed as "running" (waiting for systemctl start $service to complete), and "$service.service" and "network.target" are listed as "waiting" (for netctl@$profile.service to finish starting).