I can confirm the same issues with `systemd-networkd` in Xenial (and Debian Stretch). Do you know if there is a patch from a modern `systemd` that can be used to backport a fix to older versions?
When not using `systemd-networkd` (like older dists or "vanilla" Xenial) it is possible to see when an default route expires, but that data seems to be lost with `systemd-networkd`.
Trusty without `systemd-networkd`:
```
$ ip -6 r
[...]
default via fe80::209:fff:fe09:5 dev eth0 proto kernel metric 1024 expires 1566sec
```
Xenial without `systemd-networkd`:
```
$ ip -6 r
[...]
default via fe80::209:fff:fe09:5 dev ens192 proto ra metric 1024 expires 1545sec pref medium
```
Xenial WITH `systemd-networkd`:
```
$ ip -6 r
[...]
default via fe80::209:fff:fe09:5 dev ens192 proto ra metric 1024 pref medium
```
I can confirm the same issues with `systemd-networkd` in Xenial (and Debian Stretch). Do you know if there is a patch from a modern `systemd` that can be used to backport a fix to older versions?
When not using `systemd-networkd` (like older dists or "vanilla" Xenial) it is possible to see when an default route expires, but that data seems to be lost with `systemd-networkd`.
Trusty without `systemd-networkd`: fff:fe09: 5 dev eth0 proto kernel metric 1024 expires 1566sec
```
$ ip -6 r
[...]
default via fe80::209:
```
Xenial without `systemd-networkd`: fff:fe09: 5 dev ens192 proto ra metric 1024 expires 1545sec pref medium
```
$ ip -6 r
[...]
default via fe80::209:
```
Xenial WITH `systemd-networkd`: fff:fe09: 5 dev ens192 proto ra metric 1024 pref medium
```
$ ip -6 r
[...]
default via fe80::209:
```