ndd(1m) 맨 페이지 - 윈디하나의 솔라나라




     ndd - get and set driver configuration parameters

     ndd [-set] driver parameter [value]

     ndd gets and sets selected configuration parameters in  some
     kernel  drivers.  Currently,  ndd  only supports the drivers
     that implement the TCP/IP  Internet  protocol  family.  Each
     driver  chooses  which parameters to make visible using ndd.
     Since these parameters are usually tightly  coupled  to  the
     implementation,  they  are  likely to change from release to
     release. Some parameters may be read-only.

     Note -

       It is strongly encouraged that you use  ipadm(1M),  rather
       than ndd, to modify or retrieve TCP/IP Internet protocols.
       The current ndd command will be made obsolete in a  future
       release,  replaced by ipadm(1M). Please see NOTES for more

     If the ndd -set option is omitted,  ndd  queries  the  named
     driver,  retrieves  the  value associated with the specified
     parameter, and prints it. If the -set option is  given,  ndd
     passes  value,  which  must  be specified, down to the named
     driver which assigns it to the named parameter.

     By convention, drivers that support ndd also support a  spe-
     cial  read-only  parameter  named ``?'' which can be used to
     list the parameters supported by the driver.

     Example 1 Getting Parameters Supported By The TCP Driver

     To see which parameters are supported by the TCP driver, use
     the following command:

       example% ndd /dev/tcp \?

     The parameter name ``?'' may  need  to  be  escaped  with  a
     backslash  to  prevent its being interpreted as a shell meta

     The following  command  sets  the  value  of  the  parameter
     ip_forwarding in the dual stack IP driver to zero. This dis-
     ables IPv4 packet forwarding.

       example% ndd -set /dev/ip ip_forwarding 0

     Similarly, in order to disable IPv6 packet  forwarding,  the
     value of parameter ip6_forwarding

       example% ndd -set /dev/ip ip6_forwarding 0

     See attributes(5) for descriptions of the  following  attri-

     tab() box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i)  ATTRI-
     BUTE TYPEATTRIBUTE VALUE _ Availabilitysystem/core-os

See Also
     dladm(1M),  ipadm(1M),  ioctl(2),  attributes(5),   nca(7d),
     arp(7P), ip(7P), ip6(7P), tcp(7P), udp(7P)

     The parameters supported by  each  driver  may  change  from
     release  to release. Like programs that read /dev/kmem, user
     programs  or  shell  scripts  that  execute  ndd  should  be
     prepared for parameter names to change.

     The ioctl()  command  that  ndd  uses  to  communicate  with
     drivers  is  likely to change in a future release. User pro-
     grams should avoid making dependencies on it.

     The use of ndd to  administer  Layer  2  (Data  Link  layer)
     drivers  is strongly discouraged as this capability is to be
     obsoleted in a future release, replaced by dladm(1M). Please
     refer  to  the driver-specific man page in section 7D of the
     SunOS man pages.

     The use of ndd to administer the drivers that implement  the
     TCP/IP  Internet  protocol  family (IP/TCP/SCTP/UDP/ICMP) is
     strongly discouraged as this capability is to  be  obsoleted
     in a future release, replaced by ipadm. Please see ipadm(1M)
     for instructions for modifying and retrieving supported pro-
     tocol properties.

     The meanings of many ndd parameters make sense only  if  you
     understand how the driver is implemented.
맨 페이지 내용의 저작권은 맨 페이지 작성자에게 있습니다.