On Tue, Feb 25, 2014 at 07:51:56PM +0100, Tomasz Buchert wrote: > But, going back to our bug, it is caused by the missing DNS resolution at an > early > phase of the boot. "After=network.target" is apparently not enough to have > DNS... > I can't find any information how to ensure DNS resolution in systemd. > The workaround for now is to replace name in miredo config with its IP address > (it worked for me at least).
I had similar issue with miredo not starting under systemd today, but in my case it was caused by the tun driver not being loaded. The init.d script runs modprobe tun before starting miredo, but there is nothing similar in the miredo.service. Running modprobe tun manually helped in my case. -- pozdr(); // Jarek -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
