Kais, thanks for the note. But this is not, what I wanted to achieve. The question is, that assuming I have already a created vnic in the global zone, but nwamd should on startup *not* plumb this vnic into the global zone. I want to keep that vnic unplumbed, so that my exclusive IP-Zone can later on use this "free" vnic a interface.
Typically nwamd plumbs all network interfaces it finds, and so vnics too, and plumbs them with IP-address 0.0.0.0 into the global zone. But then all these interfaces are "lost" for later use as interfaces in exclusive-IP zones. Any ideas here ? How does others handle this ? Detlef Kais Belgaied schrieb, On 30.09.09 19:16: > Hi Detlef, > > you're encountering Bug # 6776009 nwam doesn't bring up pseudo > data-links at boot time. > > The fix is in progress. > In the meantime, the workaround suggested by Mike Lim works. > > Kais. > > On 09/30/09 08:49, Detlef Drewanz wrote: >> Hi, >> I created some vnics on my opensolaris laptop to use them later on >> with zones and virtualbox (connected via etherstub). The bad thing is, >> that every time I boot up my OpenSolaris and nwam starts, it plumb's >> all vnics into the global zone. And so I can not use these vnics for >> zones with excl. ip-instance. Has anyone managed what to do, that >> nwamd ignores these vnic's ? >> >> Thanks >> Detlef >> >> _______________________________________________ >> crossbow-discuss mailing list >> crossbow-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/crossbow-discuss >> >
