On Wed, 2009-03-25 at 15:49 -0400, Girish Moodalbail wrote: > On 03/25/09 15:36, Sebastien Roy wrote: > > But interface plumbing is irrelevant to this discussion, which is about > > the administrative objects and how the administrator interacts with > > them, and not the underlying implementation. The administrator doesn't > > care about when the interface gets plumbed as long as DHCP obtains a > > lease and configures an address. So, for example: > > > > ipadm create-interface net0 > > > > Correct. After executing the above command if the user runs > 'ifconfig', then I would presume there wouldn't be any output for > net0. It's the world where you have both 'ipadm' and 'ifconfig', and > the user using both of them interchangeably scares us.
If it's really worrisome, then I also have no problem with simply "plumbing" both IPv4 and IPv6 always. This might actually be preferable. If someone on the fringe has a problem with such a configuration, then perhaps an "ipv6-only" or "ipv4-only" interface property could be invented to appease them. > > ipadm add-address -f inet -a type=dhcp net0 > > > > 'ifconfig' would show output for 'net0' only after above command is > executed. Yep. -Seb
