On Wed, Apr 08, 2009 at 01:54:12PM -0700, Michael Hunter wrote: > On Wed, 08 Apr 2009 14:19:32 +0100 > Darren Kenny <Darren.Kenny at Sun.COM> wrote: > > > I don't think that it would matter - but it would seem to make sense that in > > attempting to set it to a multiple value that it should return an error... > > I agree about the error. I'm not so sure that it doesn''t matter. > Pragmatically you are probably right. But theoretically there could be > other protocols here besides IPv4 and IPv6. I think that should be > represented in this being a list. If it is really easy I might get a > wink more some night.
Agreed. Anurag is willing to make the changes in libnwam and in nwamcfg; I'll add this to the list of (small!) doc updates I need to make. We will make ip-version a multi-valued property; possible values are "ipv4" and "ipv6". So the line Michael was attempting (set ip-version=ipv4,ipv6) will assign both values to the property. "all" will no longer be a possible value. There are two other changes in my doc queue: 1. The DHCPv4/DHCPv6 issue: we will change the possible values for ipv4-addrsrc and ipv6-addrsrc to include only static, dhcp, and autoconf. There will no longer be separate dhcpv4 and dhcpv6 values. This change is a result of this discussion: http://mail.opensolaris.org/pipermail/nwam-dev/2009-April/000707.html 2. IP NCUs will have an enabled property. As is the case with the enabled property in Link NCUs, ENMs, and Locations, the property will be read-only; it will be changed indirectly by activating/ deactivating the NCU via nwamadm (or the nwam_ncu_[en|dis]able() functions). A '-c' option will be added to the nwamadm syntax to allow specification of an NCU class for activation, but it will not be required; 'nwamadm enable -t ncu bge0' will enable all NCUs named bge0, i.e. both the link and ip ncu if both exist. If you only want to enable the link ncu (connect a wireless link, but don't plumb ip, for example), you can use the -c option: 'nwamadm enable -t ncu -c link wpi0'. This change is a result of some discussion among the on development team; there were two main reasons for doing it: - this sort of independence will be a requirement in the future, when we will allow more complex stacking of link and ip ncus; it's better to have the concept in place from the start. - the independence could be useful immediately for debug scenarios, such as the example above, where you want to bring the link up but not plumb ip on it. -renee > > mph > > > > > Darren. > > > > On 08/04/2009 13:54, Anurag S. Maskey wrote: > > > "ip-version" is not a multi-valued property. You'd have to specify > > > "all" for both v4 and v6. > > > > > > Does it make sense to remove the "all" value and instead make the > > > "ip-version" property multi-valued? > > > > > > Anurag > > > > > > > > > Michael Hunter wrote: > > >> Why is this silently failing? > > >> > > >> nwamcfg:ncp:User:ncu:e1000g0> set ip-version=ipv4,ipv6 > > >> nwamcfg:ncp:User:ncu:e1000g0> list > > >> NCU:e1000g0 > > >> type ip > > >> class ip > > >> parent "User" > > >> ipv4-addrsrc dhcp,static > > >> ipv4-addr "10.0.5.50","10.0.5.51" > > >> ip-version ipv4 > > >> nwamcfg:ncp:User:ncu:e1000g0> > > >> _______________________________________________ > > >> nwam-dev mailing list > > >> nwam-dev at opensolaris.org > > >> http://mail.opensolaris.org/mailman/listinfo/nwam-dev > > >> > > > _______________________________________________ > > > nwam-dev mailing list > > > nwam-dev at opensolaris.org > > > http://mail.opensolaris.org/mailman/listinfo/nwam-dev > _______________________________________________ > nwam-dev mailing list > nwam-dev at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/nwam-dev
