http://defect.opensolaris.org/bz/show_bug.cgi?id=11927

           Summary: walkprop shows properties that should be skipped
    Classification: Development
           Product: nwam
           Version: RC2
          Platform: ANY/Generic
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P3
         Component: CLI
        AssignedTo: nwam-dev at opensolaris.org
        ReportedBy: Anurag.Maskey at Sun.COM
         QAContact: nwam-dev at opensolaris.org


--- Comment #0 from Anurag S. Maskey <Anurag.Maskey at Sun.COM> 2009-10-13 
20:16:28 UTC ---
walkprop shows only those properties that are necessary, unneeded properties
are skipped (but their values are not deleted (bug 11385)).  If only IPv4 is
configured, then IPv6 properties should not be displayed during the walkprop,
and vice versa.  That doesn't seem to be the case.

nwamcfg> select ncp User
nwamcfg:ncp:User> select ncu ip bge1

nwamcfg:ncp:User:ncu:bge1> walkprop
ip-version (ipv4,ipv6) [ipv4|ipv6]> ipv4
ipv4-addrsrc (dhcp) [dhcp|static]> static
ipv4-addr> 2.3.4.5/24

nwamcfg:ncp:User:ncu:bge1> list
NCU:bge1
    type                interface
    class               ip
    parent              "User"
    enabled             true
    ipv6-addrsrc        dhcp,autoconf
    ip-version          ipv4
    ipv4-addrsrc        static
    ipv4-addr           "2.3.4.5/24"

nwamcfg:ncp:User:ncu:bge1> walkprop
ip-version (ipv4) [ipv4|ipv6]> ipv6
ipv4-addr ("2.3.4.5/24")> 
ipv6-addrsrc (dhcp,autoconf) [dhcp|autoconf|static]> 

nwamcfg:ncp:User:ncu:bge1> list
NCU:bge1
    type                interface
    class               ip
    parent              "User"
    enabled             true
    ipv6-addrsrc        dhcp,autoconf
    ipv4-addrsrc        static
    ipv4-addr           "2.3.4.5/24"
    ip-version          ipv6
nwamcfg:ncp:User:ncu:bge1>

-- 
Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

Reply via email to