netdev - Re: ipv6: why disable ipv6 on last address removal?

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]

Date:	Wed, 9 Dec 2009 08:18:17 +0100
From:	Jiri Bohac <jbohac@...e.cz>
To:	David Miller <davem@...emloft.net>
Cc:	jbohac@...e.cz, netdev@...r.kernel.org, yoshfuji@...ux-ipv6.org
Subject: Re: ipv6: why disable ipv6 on last address removal?

On Tue, Dec 08, 2009 at 12:56:11PM -0800, David Miller wrote:
> From: Jiri Bohac <jbohac@...e.cz>
> > Is there any reason why inet6_addr_del needs to sets how=1 and
> > disable IPv6 even more than "ifconfig down" does?
> 
> All I can say is that this behavior is definitely on purpose, although
> I don't exactly remember why.

> Some people definitely expect no IPV6 at all in any way shape or
> form if they have not assigned IPV6 addresses to an interface.

Sure, even with how=0, IPv6 is about as much disabled as when the
interface is down. The problem is that the current behaviour goes
like this:

#1 modprobe driver_for_eth0
#2 sysctl net.ipv6.conf.tun0.aaaaaaa=b
#3 ip link set up dev eth0
#4 ip addr add xxx/yy dev eth0
#5 ip addr flush dev eth0
#6 ip link set down dev eth0 
#7 ip link set up dev eth0

#5 turns IPv6 off even deeper that it was after #1, losing the
settings made in #2.

To re-configure the settings from #2, you need to do:
#6, #7, [#6 again for some sysctl settings], #2

I think it would probably be ok for #5 to turn off IPv6 to the
state you get with #6.

Thanks,

-- 
Jiri Bohac <jbohac@...e.cz>
SUSE Labs, SUSE CZ

--
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