miredo.service fails on boot

I tried editing the unit file and replacing network.target with network-online.target worked.

```
% cat /etc/systemd/system/miredo.service
[Unit]
Description=Teredo IPv6 tunneling
After=network-online.target

[Service]
ExecStartPre=/usr/sbin/miredo-checkconf -f /etc/miredo/miredo.conf
ExecStart=/usr/sbin/miredo -f
ExecReload=/bin/kill -HUP $MAINPID

[Install]
WantedBy=multi-user.target
```

```
% LC_ALL=C systemctl status -l miredo
* miredo.service - Teredo IPv6 tunneling
   Loaded: loaded (/etc/systemd/system/miredo.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2015-08-06 09:30:27 EEST; 3min 4s ago
  Process: 1037 ExecStartPre=/usr/sbin/miredo-checkconf -f /etc/miredo/miredo.conf (code=exited, status=0/SUCCESS)
 Main PID: 1053 (miredo)
   CGroup: /system.slice/miredo.service
           |-1053 /usr/sbin/miredo -f
           |-1056 /usr/sbin/miredo -f
           `-1057 /usr/lib/x86_64-linux-gnu/miredo/miredo-privproc 4

Aug 06 09:30:27 terasar systemd[1]: Starting Teredo IPv6 tunneling...
Aug 06 09:30:27 terasar systemd[1]: Started Teredo IPv6 tunneling.
Aug 06 09:30:27 terasar miredo[1053]: Starting...
Aug 06 09:30:27 terasar miredo[1053]: miredo[1053]: Starting...
Aug 06 09:30:27 terasar miredo[1056]: New Teredo address/MTU
Aug 06 09:30:27 terasar miredo[1056]: Teredo pseudo-tunnel started
Aug 06 09:30:27 terasar miredo[1056]: (address: REMOVED, MTU: 1280)
Aug 06 09:30:27 terasar miredo[1053]: miredo[1056]: New Teredo address/MTU
Aug 06 09:30:27 terasar miredo[1053]: miredo[1056]: Teredo pseudo-tunnel started
Aug 06 09:30:27 terasar miredo[1053]: miredo[1056]: (address: REMOVED, MTU: 1280)
```

(REMOVED is not part of the output, I removed the real addresses from those spots.)

Confirmed, both the problem and the workaround, and it's present upstream too. The issue is described here:
http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
Requiring only network.target means requiring NetworkManager to start, but not requiring DNS to be up; since miredo is started before DNS is up, and it can't cope with it, the result is failure.

The possible solutions/workarounds are: 1) As per above, require network-online.target (one can use /etc/systemd/system/miredo.service.d/network-online.conf or similar override instead of editing the whole file); 2) Enable NetworkManager-wait-online (not recommended as it slows down boot); 3) Fix Miredo to wait for DNS to be up by itself.

Status changed to 'Confirmed' because the bug affects multiple users.

It's a pity but adding

network-online.target worked

to

/etc/systemd/system/miredo.service

doesn't work for me.

I've changed name address to IP after which Miredo starts well.

I've wrote in /etc/miredo/miredo.conf

# Pick a Teredo server:
#ServerAddress teredo.ipv6.microsoft.com
#ServerAddress teredo-debian.remlab.net
ServerAddress 83.170.6.76 # ip of teredo-debian.remlab.net

And in /etc/network/if-up.d/miredo

if [ "$ADDRFAM" = "ipx" ] || [ "$ADDRFAM" = "inet6" ]; then
exit 0
fi

replaced for

if [ "$ADDRFAM" = "ipx" ] || [ "$ADDRFAM" = "inet6" ]; then
ip -6 route add default dev teredo; exit 0
fi

to have miredo working on ubuntu 16.04 and 15.10

Still not fixed in 17.10.

Still is in Bionic.