Girish Moodalbail writes:
> On 03/10/09 11:47, James Carlson wrote:
> > Sowmini.Varadhan at Sun.COM writes:
> >   
> >> On (03/10/09 11:14), James Carlson wrote:
> >>     
> >>> One consideration is what to do with "ndd -set" on the global
> >>> variable.  With ip_forwarding, in addition to the global flag used for
> >>> subsequent new interfaces, we also go out and blast all of the
> >>> existing interfaces to the new setting.
> >>>
> >>> That makes the design more like my 5(a): the interface just has a
> >>> simple copy of the value created at plumb time, and you can set it on
> >>> a per-interface basis if you want.
> >>>
> >>> I dunno if that's better or worse than 5(b).  It might be close to the
> >>> noise.
> >>>       
> >> I like 5(b) better. If someone has been knowledgable enough
> >> to set the per-interface version of the prop, ndd should not go
> >> and clobber that.
> >>     
> >
> > OK.
> Well what if the end user sets the property using ipadm on all 
> interfaces, as in:
> 
> ipadm set-prop -m ip ip_def_ttl=128
> 
> Note: Currently for 'ipadm' you can either specify interface name or you 
> don't. If you specify the interface name it will be for that property. 
> But if you do specify then it's for all the interfaces.

There's a subtle issue here, which is the treatment of newly plumbed
interfaces.

If the above command affects the existing interfaces on the system,
but has no effect on the ones that may be plumbed in the future, then
I agree with you that it's a simple wildcard interface.  (I'm not sure
it's a good idea, but it's at least simple.)

If that command affects both the existing interfaces *and* sets the
value to be used for future interfaces as they're plumbed, then I
don't agree with you that it's a simple wildcard.  What you're talking
about is much more akin to the existing ip_forwarding interface.

> In that case we should allow it to be effected on all the interfaces, 
> right? Shouldn't that hold good with 'ndd' too?

I think the ndd interface should show the global value only.

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

Reply via email to