Hello, On Tue, Feb 16, 2016 at 03:54:19PM +0300, Andrey Skvortsov wrote: > your solution is not complete. At least in my case it's not enough. > There are a bit more requirements: > > 1. Add in miredo.service > After=network-online.target > Wants=network-online.target
There is one more thing missing: dependency on nss-lookup.target. As the name teredo-debian.remlab.net needs to be resolvable, the local DNS recursive resolver must be running as well (in case it is used, I'm using dnssec-trigger for that). > 2. By default network-online.target is not waiting really for the > network to come up. Depend on your configuration you need to pull into > network-online.target other services: NetworkManager-wait-online.service or > systemd-networkd-wait-online.servce. By default both services are > disabled and don't slow down boot process. > > I use NetworkManager, therefore I enabled > NetworkManager-wait-online.service and only then miredo started after the > network was really online. I can confirm that Miredo starts in my case after adding dependencies on network-online.target and nss-lookup.target (and enabling NetworkManager-wait-online.service). -- pozdr(); // Jarek
