On 25/02/16 21:06, Jarek Kamiński wrote: > 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 >
Hi Jarek, I'm still not convinced that this is the right solution. Not everybody uses NetworkManager + the fact that you need to manually enable anything seems wrong to me. A long time ago I wanted to fix the behavior of miredo to let it continue even if there are DNS errors (and retry or something). This really seems like the only way to really fix it "at the core". That said, I worked a long time ago on this. I'll have to refresh my mind about it and hopefully this time I get it done. I also welcome other people doing this for me! :D Cheers, Tomasz
signature.asc
Description: PGP signature
