From: Luca Boccassi <bluca@debian.org>
To: Serhey Popovych <serhe.popovych@gmail.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: Hans van Kranenburg <hans.van.kranenburg@mendix.com>,
898840@bugs.debian.org, netdev@vger.kernel.org
Subject: Re: [iproute2] Bug#898840: Latest update breaks ip6 default gateway cli api
Date: Wed, 16 May 2018 14:42:24 +0100 [thread overview]
Message-ID: <1526478144.23337.126.camel@debian.org> (raw)
In-Reply-To: <4de26023-48bf-fb98-2592-6fe5a6bc5c49@mendix.com>
[-- Attachment #1: Type: text/plain, Size: 1439 bytes --]
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
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next parent reply other threads:[~2018-05-16 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4de26023-48bf-fb98-2592-6fe5a6bc5c49@mendix.com>
2018-05-16 13:42 ` Luca Boccassi [this message]
2018-05-16 14:53 ` [iproute2] Bug#898840: Latest update breaks ip6 default gateway cli api Michal Kubecek
2018-05-16 16:48 ` Luca Boccassi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1526478144.23337.126.camel@debian.org \
--to=bluca@debian.org \
--cc=898840@bugs.debian.org \
--cc=hans.van.kranenburg@mendix.com \
--cc=netdev@vger.kernel.org \
--cc=serhe.popovych@gmail.com \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.