Cathy Zhou writes: > On 2009?03?23? 08:55, James Carlson wrote: > > /1...@1: -> libdladm:dladm_name2info(0xffbffd1d, 0xffbfef30, 0x0, 0x0) > > /1...@1: <- libdladm:dladm_name2info() = 5 > > > > ... and that's because the link just doesn't exist here. > > I thought this will be fixed by Seb as part of his iptun work. See bug > 6509231.
It might make the link present, but I guess I'd be surprised if it actually allowed datalink changes for aggregations to be done from inside a non-global zone. The infrastructure belongs to the global zone, not the non-global zone. Even when you give a link to zone, you're not giving over the entire physical link. For example, the global zone can still create VNICs on top of the same physical link and (potentially) give those to other zones. Having all of the non-global zones with access to a link be able to modify basic link properties and configuration doesn't sound right to me. Am I missing something? I had thought I understood how "exclusive *IP* stack instances" were supposed to work, but now you're making me doubt my understanding. What exactly is the administrative model? Who owns what, and what precisely does "add net" do? -- James Carlson, Solaris Networking <[email protected]> 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 _______________________________________________ networking-discuss mailing list [email protected]
