Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 8 Mar 2010 19:48:06 +0000 (UTC)
From:      "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
To:        freebsd-rc@FreeBSD.org
Cc:        freebsd-net@freebsd.org
Subject:   Re: Un-obsolete'ing ipv6_enable
Message-ID:  <20100308193942.W33454@maildrop.int.zabbadoz.net>
In-Reply-To: <4B945AA7.6070000@FreeBSD.org>
References:  <4B945AA7.6070000@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 7 Mar 2010, Doug Barton wrote:

Hi,

> As we've previously discussed, I would like to un-obsolete ipv6_enable,
> and return it to the status of being the knob that actually controls
> whether or not we configure IPv6. My understanding is that the consensus
> is in agreement with this change, however I'm posting my proposed patch
> (minus the rc.conf(5) change) just in case. If you have any objection,
> please speak up sooner rather than later.

I am not sure where the previous discussion happened anymore but I
veto to bring back ipv6_enable this way.  It's not going to do what
you promise above.

It will be utterly confusing for people to have
 	ipv6_enable="NO"
 	ifconfig_if0_ipv6="inet6 2001:db8::1/64"
and find that IPv6 is still enabled and working on if0.

Further I can no longer find a way to say "accept rtadv messages on the
upstream interface but by default do not on any other of the
interfaces while still having IPv6 enabled" unless I configure an
ifconfig_ifN_ipv6="..." for all of them.

I would immediately vote for removing the backward stuff to cleanup
the code though.

/bz

-- 
Bjoern A. Zeeb         It will not break if you know what you are doing.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100308193942.W33454>