Cathy> I ... found that the network/nwam service does exist in the local Cathy> zone. It also has a function call lookup_zonename() in its code.
Kacheong> Oh, I think it is a fix to make sure that only the dhcpagent in Kacheong> the zone running nwamd (which is the global zone) is killed, not Kacheong> the dhcpagent in other zones. Correct. Kacheong> I don't think it is the intention to run nwamd in a non-global Kacheong> zone. I guess John can confirm this. The network/nwam leak to Kacheong> a non-global zone is probably a bug. Not correct. Quoting /lib/svc/method/net-nwam: # In a shared-IP zone we need this service to be up, but all of the work # it tries to do is irrelevant (and will actually lead to the service # failing if we try to do it), so just bail out. # In the global zone and exclusive-IP zones we proceed. In other words, for traditional (pre IP instances) local zones, you would have been correct, but since IP instances came into being, local zones are split into two types: shared IP and exclusive IP. In shared IP zones, network configuration is specified by zonecfg in the global zone; in exclusive IP zones, nwamd should (in theory) just work. However (in practice), there may well be issues to be worked out, such as those which Cathy mentioned in the first message in this thread. We (the NWAM team, probably in conjunction with the dladm and WPA teams) need to look into those. -- John http://blogs.sun.com/jbeck
