netdev - Re: Cannot set IPv6 address

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 for Android: free password hash cracker in your pocket

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

Message-ID: <1479310198.8455.199.camel@edumazet-glaptop3.roam.corp.google.com>
Date:   Wed, 16 Nov 2016 07:29:58 -0800
From:   Eric Dumazet <eric.dumazet@...il.com>
To:     Saeed Mahameed <saeedm@....mellanox.co.il>
Cc:     david.lebrun@...ouvain.be,
        Linux Netdev List <netdev@...r.kernel.org>,
        Doron Tsur <doront@...lanox.com>,
        Majd Dibbiny <majd@...lanox.com>
Subject: Re: Cannot set IPv6 address

On Wed, 2016-11-16 at 17:22 +0200, Saeed Mahameed wrote:
> Hi David,
> 
> The following commit introduced a new issue when setting IPv6 address
> via the following command:
> 
> /sbin/ip -6 addr add 2001:0db8:0:f112::1/64 dev enp2s2
> RTNETLINK answers: Operation not supported
> 
> Offending commit:
> 
> commit 6c8702c60b88651072460f3f4026c7dfe2521d12
> Author: David Lebrun <david.lebrun@...ouvain.be>
> Date:   Tue Nov 8 14:57:41 2016 +0100
> 
>     ipv6: sr: add support for SRH encapsulation and injection with lwtunnels
> 
>     This patch creates a new type of interfaceless lightweight tunnel (SEG6),
>     enabling the encapsulation and injection of SRH within locally emitted
>     packets and forwarded packets.
> 
>     >From a configuration viewpoint, a seg6 tunnel would be configured
> as follows:
> 
>       ip -6 ro ad fc00::1/128 encap seg6 mode encap segs
> fc42::1,fc42::2,fc42::3 dev eth0
> 
>     Any packet whose destination address is fc00::1 would thus be encapsulated
>     within an outer IPv6 header containing the SRH with three
> segments, and would
>     actually be routed to the first segment of the list. If `mode inline' was
>     specified instead of `mode encap', then the SRH would be directly inserted
>     after the IPv6 header without outer encapsulation.
> 
>     The inline mode is only available if CONFIG_IPV6_SEG6_INLINE is
> enabled. This
>     feature was made configurable because direct header insertion may break
>     several mechanisms such as PMTUD or IPSec AH.
> 
>     Signed-off-by: David Lebrun <david.lebrun@...ouvain.be>
>     Signed-off-by: David S. Miller <davem@...emloft.net>
> 
> 
> Can you check ? Are we missing something here ?

Sure, patch is under review. Please look at netdev archives and/or
ozlabs

https://patchwork.ozlabs.org/patch/695060/