>> But then, if someone has created configuration on a non-existent >> interface, and later the underlying datalink for that interface is >> added to the system, how does one activate the latent configuration? >> E.g., the net-physical script will need something like "ipadm >> create-interface", or "ipadm init-intfprop <intf>" to create >> the interface and apply the latent configuration. > > That is an implementation matter, right? > For dladm we solve it my keeping the properties for missing interfaces > in user space and some upcall to retrieve them when the object comes > into existence. One could do the same for these missing objects, or one
But dladm doesn't allow you to create configuration for a missing interface today, right (it only reapplies previously created config, and the first creation requires the interfce to be present)? My question was: if we have a way of creating configuration for missing objects, and the admin creates this virtual configuration, then what is the administrative step to actually enable that configuration. I was thinking of "ipadm create-link" as a way of applying the virtual config. (But I think what you are suggesting is to have the actual datalink create/rename commands itself apply this?) > We probably have a lot more non-universal properties in dladm than in > ipadm. But I can think of one for ipadm. > > I setup the system with link1 being a pt-pt interface. > Thus I do some > ipadm create-address destination=10.2.2.2 link1/10.1.1.1 > > Then link1 disappears. > When it reappears, whether or not Vanity naming is involved, it is no > longer a pt-pt type link. > > What we'd want for those cases is that the whole create-address that is > triggered by the link reappearing fail. We don't want e.g., that the > address is created and the local address is set, but the destination is > not set. > > And we'd need some place to report these errors. right, there would have to be a lot of error-checking. --Sowmini _______________________________________________ networking-discuss mailing list [email protected]
