Peter Memishian wrote:
> > > - Property/tunable management:
> > >
> > > # ipadm {set,get}-module-prop -p <name>=<value> [<interface>]
> > >
> > > If no <interface> is specified, the property is set for all active
> > > interfaces.
> >
> > You also need to answer what happens to interfaces that are created
> > after a property has been set. For instance, I might want to turn on
> > forwarding on all current and future interface.
>
> I figured that was handled by having "<interface>" be optional -- e.g.,
> the admin can set a global default, but also provide overrides for
> specific (extant) interfaces.
There is a difference between
All current interfaces
and
All current and all future interfaces
The text above reads as the first one.
I think we need the second one. I don't know if there is a case for the
first one as well, or if the second one is sufficient.
Erik
> We could go further and allow settings for objects that don't exist, but
> that both makes the implementation more complex and could surprise (e.g.,
> admin types net3 instead of net2, and it's accepted but silently does
> nothing until net3 shows up a year later. Meanwhile, net2 had the wrong
> settings all along. While we can't stamp out the impact of typos from the
> system, I'd like to have a clear benefit to balance out the risk).
>
