On Tue, Apr 07, 2009 at 07:58:06AM -0400, James Carlson wrote:
> Michael Hunter writes:
> > nwam_addrsrc_t has entries NWAM_ADDSRC_{DHCP, DCPV6, AUTOCONF,
> > STATIC}. I initially thought that for NWAM_NCU_PROP_IPV4_ADDRSRC DHCP
> > and STATIC would be valid configuration. But on second thought if the
> > intention was for STATIC to be a shared configuration option between
> > IPv4 and IPv6 then why isn't DHCP? Is this just because the sense of
> > the option is different?
>
> I would have expected to have separate address source controls for v4
> and v6 on a given interface, rather than a single combined control as
> that list seems to suggest. The behavior of v4 and v6 is slightly
> different in a number of areas.
There are separate properties for v4 and v6 address source(s); but
both properties are of type nwam_addrsrc_t (and can be multi-valued).
The default value for v4 addrsrc is DHCP; the default for v6 addrsrc
is DHCPV6 and AUTOCONF. For v6, the expectation is that DHCPV6 and
AUTOCONF will generally be there, but since solaris does allow you
to turn off the use of those today, we chose to leave that option in.
In reply to Michael's original question: nwam_addrsrc_t is a shared
enum, used for both the v4 and v6 addrsrc properties. STATIC is an
equally valid option for both v4 and v6. I don't think we ever
discussed whether we should have separate DHCPV4 and DHCPV6 values;
I'd imagine whoever wrote up the list (probably me or Alan, but I
can't remember) made separate DHCP items because they really are
separate protocols, they represent two fairly different approaches
to getting an address. I don't suppose they need to be separate;
it's obvious which protocol is intended based on which property the
value is assigned to. Do you have a preference?
-renee
