All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Michal Kubecek <mkubecek@suse.cz>, netdev@vger.kernel.org
Cc: Serhey Popovych <serhe.popovych@gmail.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	Hans van Kranenburg <hans.van.kranenburg@mendix.com>,
	898840@bugs.debian.org
Subject: Re: [iproute2] Bug#898840: Latest update breaks ip6 default gateway cli api
Date: Wed, 16 May 2018 17:48:57 +0100	[thread overview]
Message-ID: <1526489337.23337.127.camel@debian.org> (raw)
In-Reply-To: <20180516145344.fle2t7qng7cvowsu@unicorn.suse.cz>

[-- Attachment #1: Type: text/plain, Size: 789 bytes --]

On Wed, 2018-05-16 at 16:53 +0200, Michal Kubecek wrote:
> On Wed, May 16, 2018 at 02:42:24PM +0100, Luca Boccassi wrote:
> > 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.
> 
> Fixed already:

Ah fantastic, thanks, sorry I missed that.

-- 
Kind regards,
Luca Boccassi

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2018-05-16 16:49 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 ` [iproute2] Bug#898840: Latest update breaks ip6 default gateway cli api Luca Boccassi
2018-05-16 14:53   ` Michal Kubecek
2018-05-16 16:48     ` Luca Boccassi [this message]

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=1526489337.23337.127.camel@debian.org \
    --to=bluca@debian.org \
    --cc=898840@bugs.debian.org \
    --cc=hans.van.kranenburg@mendix.com \
    --cc=mkubecek@suse.cz \
    --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.