netdev - Re: [PATCH net-next] net: ipv6: put autoconf routes into per-interface tables

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAKD1Yr21W2Ce6mhAqfz+mFUPTn+xn3K_Lz2q5LA27f6V=9tTSQ@mail.gmail.com>
Date:   Tue, 10 Jan 2017 11:29:40 +0900
From:   Lorenzo Colitti <lorenzo@...gle.com>
To:     David Ahern <dsa@...ulusnetworks.com>
Cc:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        Maciej Żenczykowski <zenczykowski@...il.com>,
        Hannes Frederic Sowa <hannes@...essinduktion.org>,
        Erik Kline <ek@...gle.com>,
        YOSHIFUJI Hideaki <hideaki.yoshifuji@...aclelinux.com>,
        David Miller <davem@...emloft.net>,
        Daniel Rosenberg <drosen@...gle.com>, temnota.am@...il.com
Subject: Re: [PATCH net-next] net: ipv6: put autoconf routes into
 per-interface tables

On Tue, Jan 10, 2017 at 11:08 AM, David Ahern <dsa@...ulusnetworks.com> wrote:
> That's news to me. What about IPv6 and VRF is not working or well-supported?

I have no firsthand experience of this myself, but if the problems
that Andrey reports above in this thread are real, then those would
indicate that the code is not well-supported. Being unable to accept
DAD is a pretty serious issue. Andrey, what version of the kernel did
you see this on?