Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 09 Mar 2010 13:59:17 +0900 (JST)
From:      Hiroki Sato <hrs@FreeBSD.org>
To:        dhorn2000@gmail.com
Cc:        freebsd-net@FreeBSD.org, dougb@FreeBSD.org, freebsd-rc@FreeBSD.org
Subject:   Re: Un-obsolete'ing ipv6_enable
Message-ID:  <20100309.135917.161082188.hrs@allbsd.org>
In-Reply-To: <25ff90d61003082037v3519995bx7e119e9d14143db4@mail.gmail.com>
References:  <4B945AA7.6070000@FreeBSD.org> <20100309.072719.200228546.hrs@allbsd.org> <25ff90d61003082037v3519995bx7e119e9d14143db4@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
----Security_Multipart(Tue_Mar__9_13_59_17_2010_019)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

David Horn <dhorn2000@gmail.com> wrote
  in <25ff90d61003082037v3519995bx7e119e9d14143db4@mail.gmail.com>:

dh> The question is what is the desired end-state for the rc.conf
dh> configuration of ipv6 ?
dh>
dh> Do we want to have a per-interface setting required to enable ipv6 SLAAC ?
dh> Do we want to have a global setting for ipv6 SLAAC ?
dh> Or do we want to choose sane defaults and allow the user to over-ride
dh> on both a global default, and a per-interface basis ?
dh>
dh> So, in the 8.0-RELEASE code (and previous TTBOMK), both IPv4 DHCP and
dh> IPv6 SLAAC required manual enabling, although it was inconsistent in
dh> that one was global (IPV6 accept_rtadv), and one was per-interface
dh> (IPv4 DHCP).  Some of this has already started to change in -current.
dh>
dh> Question 1)  Based upon history, sane defaults would be do nothing (NO
dh> DHCPv4, NO IPv6 accept_rtadv).  Do you agree with this as the
dh> continued defaults ?

 I am for "no automatic configuration unless one specifies it", but it
 should be able to be configured in a per-interface basis as well as
 global basis.

dh> Question 2) Assuming that people do desire consistency with allowing
dh> for both a global, and a per-interface setting, do you agree with
dh> having a global default for DHCPv4 (dhcpv4_default_enable), and for
dh> IPv6 slaac/accept_rtadv  (ipv6-slaac_default_enable), and the
dh> per-interface DHCPv4 (ifconfig_IF0="dhcp") aka a meta configuration
dh> variable, and a per-interface IPv6 slaac (ifconfig_IF0="slaac") aka a
dh> meta configuration variable.

 I think the global configuration can be realized by setting something
 like ifconfig_DEFAULT_<proto>="AUTO" instead of adding a new global
 knobs.

dh> Do people understand what I am proposing here, or do you want me to
dh> put together a diff with an implementation to properly review ?   I
dh> already have some of it working in a separate experiment for adding
dh> DHCPv6 configurations.

 Yeah, actually I received your proposal a month ago and I should have
 put it to the wiki or so.  Sorry about that.  I will work on that
 soon for the further discussion.

-- Hiroki

----Security_Multipart(Tue_Mar__9_13_59_17_2010_019)--
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)

iEYEABECAAYFAkuV1aUACgkQTyzT2CeTzy0T+ACfSfB0DRdhLNDDKV/Hyx9FCapZ
lc4An33sS6Ri6tmKdvUrDmSVYvcq+S/l
=fl5R
-----END PGP SIGNATURE-----

----Security_Multipart(Tue_Mar__9_13_59_17_2010_019)----



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