netdev - Re: radvd and auto-ipv6 address regression from 2.6.31 to 2.6.34+

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: <alpine.DEB.1.10.1011060713290.2639@uplift.swm.pp.se>
Date:	Sat, 6 Nov 2010 07:17:41 +0100 (CET)
From:	Mikael Abrahamsson <swmike@....pp.se>
To:	Ben Greear <greearb@...delatech.com>
cc:	NetDev <netdev@...r.kernel.org>
Subject: Re: radvd and auto-ipv6 address regression from 2.6.31 to 2.6.34+

On Fri, 5 Nov 2010, Ben Greear wrote:

>> On hacked 2.6.34 and 2.6.36 kernels, however, the veth0 gains a new 
>> address that appears to be generated similar to other IPs associated 
>> with auto-creation via radvd.
>> 
>> I have not yet tested intervening kernels or physical interfaces between
>> two machines.
>> 
>> So, the question is: Is the new behaviour on purpose, or is it a
>> regression bug?
>
> Actually, this doesn't seem to work for 2.6.31 either, so I guess it
> isn't a regression.
>
> Is it expected behaviour, however?

I would not be surprised if the IPv6 stack on Linux would gain IPv6 
addresses using SLAAC from any interface if it sees RAs on it, regardless 
if these are locally generated or not.

I guess any Linux device running radvd should turn off autoconf on those 
interface that radvd is acting on?

net.ipv6.conf.veth0.accept_ra=0 should do the trick?

-- 
Mikael Abrahamsson    email: swmike@....pp.se
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html