Bug#924575: systemd-networkd doesn't process IPv6 RA properly

[Johan Wassberg]

> On 15 Mar 2019, at 08:37, Johan Wassberg <jocar at su.se> wrote:
> 
>> (would be great if you cant test this version and report back)
> 
> Will see what we can accomplish in the lab!

systemd(-networkd) 241-1~bpo9+1 from stretch-backports seems to work
better.
The expiration is now present in the output from `ip -6 r` and the
route is discarded when the timer runs out:
```
2001:dead:5:1219::/64 dev ens33 proto ra metric 1024  expires 2591574sec pref medium
fe80::/64 dev ens33 proto kernel metric 256  pref medium
default via fe80::209:fff:fe09:5 dev ens33 proto ra metric 1024  expires 1374sec mtu 1500 pref medium
```

But both the new version of systemd-networkd and the default network
service "networking" (not sure of the official name is) will add more
then one default route if the router advertise this.
Is this a feature or a bug?

It is not possible to and another default route via `ip -6 route`:
```
# ip -6 route add default via default via fe80::dead:beef:dead:beef dev ens33
RTNETLINK answers: File exists
```

Still curious, is systemd-networkd in stretch-backports considered stable?

--
jocar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190318/4863f618/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190318/4863f618/attachment.sig>