From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luca Boccassi Subject: Re: [iproute2] Bug#898840: Latest update breaks ip6 default gateway cli api Date: Wed, 16 May 2018 14:42:24 +0100 Message-ID: <1526478144.23337.126.camel@debian.org> References: <4de26023-48bf-fb98-2592-6fe5a6bc5c49@mendix.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-v2OunpYuqKKmshpH+eFg" Cc: Hans van Kranenburg , 898840@bugs.debian.org, netdev@vger.kernel.org To: Serhey Popovych , Stephen Hemminger Return-path: Received: from mail-wr0-f181.google.com ([209.85.128.181]:43061 "EHLO mail-wr0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751395AbeEPNm3 (ORCPT ); Wed, 16 May 2018 09:42:29 -0400 Received: by mail-wr0-f181.google.com with SMTP id v15-v6so1237200wrm.10 for ; Wed, 16 May 2018 06:42:28 -0700 (PDT) In-Reply-To: <4de26023-48bf-fb98-2592-6fe5a6bc5c49@mendix.com> Sender: netdev-owner@vger.kernel.org List-ID: --=-v2OunpYuqKKmshpH+eFg Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, 2018-05-16 at 14:26 +0200, Hans van Kranenburg wrote: > Package: iproute2 > Version: 4.16.0-2 > Severity: normal >=20 > Hi, >=20 > The last iproute2 update has a backwards incompatible change in > setting > IPv6 default routes, breaking existing configuration and scripts. >=20 > Previously, the following was possible, and now it requires an > explicit > -6 option to be added: >=20 > -# ip route add default via 2001:db8::1 dev eth0 > Error: inet address is expected rather than "2001:db8::1". >=20 > This works: > -# ip -6 route add default via 2001:db8::1 dev eth0 >=20 > I found out after having systems end up being unreachable after a > reboot, because I have commands like these in network/interfaces. >=20 > 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! --=20 Kind regards, Luca Boccassi --=-v2OunpYuqKKmshpH+eFg Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEE6g0RLAGYhL9yp9G8SylmgFB4UWIFAlr8NUAACgkQSylmgFB4 UWJvAAgAuSftnihOFd6xA0QQpVKe7Gjj/aY/8JGBrl+JXmGZFgij7BRc8v8vSTaV +b5OJoptVz9Bmg6d84L1l53oqL7PcSgygoZNeDJoPhOVXpnc/JMrUU8j7+B8SRn5 ICq3O6dHoXLlFH5j68AmJqLe5Qk60TMiv5uVmZEONfLD3YlSdmQhztruwB6zMFqd jIbNeBh318xR+wFfoBXxQTpbObISThpWGDG+GMQ0gFPqQzNIFOUI3zzYaagqLW3X ipjqCqW2DOQE2o4Bn/aRa7gMHgwjwTxZtc9BbRLiq7Fwtr/JGReBr18d5JZtGkpS pA5G7Eqns50es26mMI0K1IFumORWmw== =iBNF -----END PGP SIGNATURE----- --=-v2OunpYuqKKmshpH+eFg--