Alex Zhang wrote: > Hi all, > Is an ip ncu must related to a physical link ncu, and their name must the > same? > However, in the latest version of bfu, I can create an ip ncu named ncu0, and > an phys > ncu named ncu1, and no other ncu existed. Is it correct? > > At present, there is nothing tying the NCUs to the physical links present on the machine. I think hat this makes sense, since it's possible an administrator might want to either prepare a configuration for a physical device not yet present, or a configuration might refer to a device that has since been removed. So the behaviour you've described is okay. What nwamd will do on startup or on device hotplug is create datalink and IP NCUs in the automatic and user NCPs corresponding to the links it finds on the system. The user can add additional NCUs, but they won't do anything.
One thing we need to do is tighten validation of NCU names - since these need to at least potentially refer to underlying links, they need to end in a number (even if a link is renamed, it needs an instance number on the end, e.g. wired0). I'm working on those changes at the moment, so they're not there yet. Alan
