On Wed, 2018-05-16 at 14:26 +0200, Hans van Kranenburg wrote: > Package: iproute2 > Version: 4.16.0-2 > Severity: normal > > Hi, > > The last iproute2 update has a backwards incompatible change in > setting > IPv6 default routes, breaking existing configuration and scripts. > > Previously, the following was possible, and now it requires an > explicit > -6 option to be added: > > -# ip route add default via 2001:db8::1 dev eth0 > Error: inet address is expected rather than "2001:db8::1". > > This works: > -# ip -6 route add default via 2001:db8::1 dev eth0 > > I found out after having systems end up being unreachable after a > reboot, because I have commands like these in network/interfaces. > > I had a look at upstream changelogs, but I don't see any mention of > this, and suspect it was not intentional. However, it's bad.
Hello Serhey and Stephen, Hans reported a regression in v4.16.0, ip route now requires -6 to be manually added when using v6 addresses while up to 4.15 it didn't, the commands quoted show the problem. Bisecting shows that the following commit from Serhey introduced the problem: 93fa12418dc6f5943692250244be303bb162175b utils: Always specify family and ->bytelen in get_prefix_1() Could you please have a look when you have a moment? It's very easy to reproduce, and it breaks existing scripts and so on. Thanks! -- Kind regards, Luca Boccassi
signature.asc
Description: This is a digitally signed message part
