Sebastien Roy wrote:
Yes, there is utility in this. My statement was meant to suggest that
some aspects of address management could potentially occur without
explicit configuration. If that doesn't fit the model we're going for,
then that's fine.
I'd expect the system as a whole, in particular with NWAM, to do the
right thing.
Even without NWAM I'd expect the installer to allow static or DHCPv4 for
IPv4, and just enable IPv6 as today.
Nobody is proposing changing that as far as I know.
Instead we are talking about the objects visible in ipadm and how to
make that the intuitive, simple in the simple cases, yet have sufficient
flexibility.
Good points. Note that I agree that "logical interface" as an
administrative object should not be carried forward.
Going once, going twice ... ;-)
Also, once an address has been created by whatever means, I don't see
why <IP interface, IP address> wouldn't be sufficient to identify it
(even dynamically created ones).
Building a house on shifting sand; the address can change due to
ND/DHCPv* at any time.
And it would be odd if I did
ipadm create-dynamic-ipv6 -i bge0
which configured N addresses, and then ipadm allows me to selectively
destroy those addresses.
What would the semantics be for such a destroy? That such an address can
never be re-added by ndpd/dhcpclient, even 3 months later and after
having visited 17 different networks? Or just while I'm connected to the
current network??
Doing
ipadm destroy-dynamic-ipv6 -i bge0
means that there is no IPv6 link-local, no stateless, and no DHCPv6
operating for the default IID on that interface.
(But the model allows multiple IIDs, in which case the above destroy
wouldn't have any effect on those IIDs.)
Erik
_______________________________________________
networking-discuss mailing list
[email protected]
