plcset.1.html 14 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233
  1. <?xml version='1.0' encoding='iso-8859-1'?>
  2. <!doctype html public '-//W3C//DTD XHTML 1.0 Strict//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd'>
  3. <html xmlns='http://www.w3c.org/1999/xhtml' lang='en-us'>
  4. <head>
  5. <title>
  6. plcset.1
  7. </title>
  8. <meta http-equiv='content-type' content='text/html;iso-8859-1'/>
  9. <meta name='generator' content='motley-tools 1.9.4 13:40:33 Feb 18 2015'/>
  10. <meta name='author' content='cmaier@cmassoc.net'/>
  11. <meta name='robots' content='noindex,nofollow'/>
  12. <link href='toolkit.css' rel='stylesheet' type='text/css'/>
  13. </head>
  14. <body>
  15. <div class='headerlink'>
  16. [<a href='plcrule.1.html' title=' plcrule.1 '>PREV</a>]
  17. [<a href='toolkit.html' title=' Index '>HOME</a>]
  18. [<a href='plcstat.1.html' title=' plcstat.1 '>NEXT</a>]
  19. </div>
  20. <pre>
  21. plcset(1) Qualcomm Atheros Open Powerline Toolkit plcset(1)
  22. NAME
  23. plcset - Qualcomm Atheros PLC Set Property
  24. SYNOPSIS
  25. plcset [options] [type data] [type data] [device] [device] [...]
  26. DESCRIPTION
  27. Set a specific property value on an Qualcomm Atheros powerline device using the VS_SET_PROPERTY message. Properties are
  28. specified using their numeric property identifier. Property names are not supported. Property values are entered using
  29. type and data pairs. Users familiar with program setpib should already understand this method of entering data values.
  30. Only selected properties can be set using this message type. See the Qualcomm Atheros Firmware Technical Reference Man‐
  31. ual for supported property identifiers, versions, values and data formats.
  32. This program is part of the Qualcomm Atheros Powerline Toolkit.
  33. OPTIONS
  34. -e Redirects stderr messages to stdout. By convention status and error messages are printed on stderr while primary
  35. program output is printed on stdout. This option prints all output on stdout in cases where this is desired.
  36. -n number
  37. The property identifier or peoperty version. Property identifiers and versions are entered as 32-bit decimal
  38. integers. Property names are not supported. The default is 0. This option may appear more than once on the com‐
  39. mand line. The first occurance specifies the property identifier. The second occurances specifies the property
  40. version. See the Firmware Technical Reference Manual for an list of valid property identifiers and versions.
  41. -i interface
  42. Select the host Ethernet interface. All requests are sent via this interface and only reponses received via this
  43. interface are recognized. The default interface is eth1 because most people use eth0 as their principle network
  44. connection; however, if environment string &quot;PLC&quot; is defined then it takes precedence over the default interface.
  45. This option then takes precedence over either default.
  46. -o option
  47. The update option (or method) expressed as an 8-bit hexadecimal integer. The prefix &quot;0x&quot; is optional. Option
  48. values are constructed from the logical OR of 0x01=ApplyNow, 0x02=Persist and 0x04=Reset. The only legal option
  49. values are 0x01, 0x02, 0x03 and 0x06.
  50. -q Suppresses status messages on stderr.
  51. -v Prints additional information on stdout. In particular, this option dumps outgoing Ethernet packets on stdout.
  52. -?,--help
  53. Displays program help information on stderr. This option takes precedence over all other options on the command
  54. line except version information.
  55. -!,--version
  56. Displays program version information on stderr. This option takes precedence over all other options on the com‐
  57. mand line except help information. Use this option when sending screen dumps to Atheros technical staff.
  58. ARGUMENTS
  59. device The MAC address of some powerline device. More than one address may be specified. If more than one address is
  60. specified then operations are performed on each device in turn. The default address is local. See DEVICES for
  61. information about symbolic device addresses.
  62. FORMATS
  63. Each property is assigned one or more values. Each value may have a different type and size. The expected type, size
  64. and order of property values is described in the Firmware Technical Reference Manual under the VS_SET_PROPERTY message
  65. description. Expected data types and values must be entered on the command line in the order specified in the manual and
  66. must appear on the command line before any device addresses appear.
  67. byte integer
  68. An unsigned integer stored as 8 bits or 1 byte. The value is expressed in decimal by default. A binary value may
  69. be expressed with a 0b prefix. A hexadecimal value may be expressed using a 0x prefix. The offset increments by
  70. 1 prior to the next insertion.
  71. word integer
  72. An unsigned integer stored as 16 bits or 2 bytes. The value is expressed in decimal by default. A binary value
  73. may be expressed with a 0b prefix. A hexadecimal value may be expressed using a 0x prefix. The result will be
  74. sent in little endian byte order. The offset increments by 2 prior to the next insertion.
  75. long integer
  76. An unsigned integer stored as 32 bits or 4 bytes. The value is expressed in decimal by default. A binary value
  77. may be expressed with a 0b prefix. A hexadecimal value may be expressed using a 0x prefix. The result will be
  78. sent in little endian byte order. The offset increments by 4 prior to the next insertions.
  79. huge integer
  80. An unsigned integer stored as 64 bits or 8 bytes. The value is expressed in decimal by default. A binary value
  81. may be expressed with a 0b prefix. A hexadecimal value may be expressed using a 0x prefix. The offset increments
  82. by 8 prior to the next insertion. The result will be sent in little endian byte order. This type is only avail‐
  83. able on hosts that support 64 bit data values.
  84. data hex
  85. A sequence of hexadecimal octets. Octets may be separated by a colon for clarity. The number of octets deter‐
  86. mines the number of bytes written. The result is sent in the byte order specified on the command line. The off‐
  87. set increments by the number of bytes written. This is similar to &quot;key&quot; and &quot;mac&quot; below but accepts variable
  88. length input.
  89. key hex
  90. A sequence of hexadecimal octets. Octets may be separated by a colon for clarity. The number of octets must con‐
  91. vert to 16 bytes or an error will occur. The result is sent in the byte order specified on the command line. The
  92. offset increments by 16 prior to the next insertion. This is similar &quot;data&quot; above but accepts ony fixed length
  93. input. This option may be used to set the DAK, NMK or NVAK values.
  94. mac hex
  95. A sequence of hexadecimal octets. Octets may be separated by a colon for clarity. The number of octets must con‐
  96. vert to 6 bytes or an error will occur. The result is sent in the byte order specified on the command line. The
  97. offset increments by 6 prior to the next insertion. This is similar &quot;data&quot; above but accepts only fixed length
  98. input. This option may be used to set the DAK, NMK or NVAK values.
  99. hfid string
  100. An ASCII character string. The string is always stored as 64 bytes. Short strings are padded on the right with
  101. NUL characters. Long strings are truncated on the right and the last byte is forced to NUL. The offset incre‐
  102. ments by 64 prior to the next insertion. This option may be used to enter user, network and manufacturer identi‐
  103. fication strings.
  104. zero count
  105. An unsigned integer representing the number of consecutive bytes to fill with 0x00. The offset increments by the
  106. number of bytes written. This option may be used to erase regions of the PIB.
  107. fill count
  108. An unsigned integer representing the number of consecutive bytes to fill with 0xFF. The offset increments by the
  109. number of bytes written. This option may be used to erase regions of the PIB.
  110. skip count
  111. An unsigned integer indicating the number of bytes to skip over before staring another change. Intervening data
  112. data locations are unchanged.
  113. TR69 DATA TYPES
  114. These data types are not currently recognized by the runtime firmware and so errors will certainly result if they are
  115. used.
  116. accesspassword string
  117. An ASCII character string. The string is always stored as 257 bytes. Short strings are padded on the right with
  118. NUL characters. Long strings are truncated on the right and the last byte is forced to NUL. The offset incre‐
  119. ments by 257 prior to the next insertion.
  120. accessusername string
  121. An ASCII character string. The string is always stored as 33 bytes. Short strings are padded on the right with
  122. NUL characters. Long strings are truncated on the right and the last byte is forced to NUL. The offset incre‐
  123. ments by 33 prior to the next insertion.
  124. adminpassword string
  125. An ASCII character string. The string is always stored as 33 bytes. Short strings are padded on the right with
  126. NUL characters. Long strings are truncated on the right and the last byte is forced to NUL. The offset incre‐
  127. ments by 33 prior to the next insertion.
  128. adminusername string
  129. An ASCII character string. The string is always stored as 33 bytes. Short strings are padded on the right with
  130. NUL characters. Long strings are truncated on the right and the last byte is forced to NUL. The offset incre‐
  131. ments by 33 prior to the next insertion.
  132. password string
  133. An ASCII character string. The string is always stored as 257 bytes. Short strings are padded on the right with
  134. NUL characters. Long strings are truncated on the right and the last byte is forced to NUL. The offset incre‐
  135. ments by 257 prior to the next insertion.
  136. url string
  137. An ASCII character string. The string is always stored as 257 bytes. Short strings are padded on the right with
  138. NUL characters. Long strings are truncated on the right and the last byte is forced to NUL. The offset incre‐
  139. ments by 257 prior to the next insertion.
  140. username string
  141. An ASCII character string. The string is always stored as 257 bytes. Short strings are padded on the right with
  142. NUL characters. Long strings are truncated on the right and the last byte is forced to NUL. The offset incre‐
  143. ments by 257 prior to the next insertion.
  144. DEVICES
  145. Powerline devices use Ethernet Media Access Control (MAC) addresses. A MAC address is a 48-bit value entered as 12 hexa‐
  146. decimal digits in upper, lower or mixed character case. Octets may be separated with colons for clarity. For example,
  147. &quot;00b052000001&quot;, &quot;00:b0:52:00:00:01&quot; and &quot;00b052:000001&quot; are valid and equivalent.
  148. The following MAC addresses are special and may be entered by name instead of number.
  149. all Same as &quot;broadcast&quot;.
  150. broadcast
  151. A synonym for the Ethernet broadcast address, FF:FF:FF:FF:FF:FF. All devices, whether local, remote or foreign
  152. recognize messages sent to this address. A remote device is any device at the far end of a powerline connection.
  153. A foreign device is any device not manufactured by Atheros.
  154. local A synonym for the Qualcomm Atheros vendor specific Local Management Address (LMA), 00:B0:52:00:00:01. All local
  155. Atheros devices recognize this address but remote and foreign devices do not. A remote device is any device at
  156. the far end of a powerline connection. A foreign device is any device not manufactured by Atheros.
  157. REFERENCES
  158. See the Qualcomm Atheros HomePlug AV Firmware Technical Reference Manual for the latest information on available proper‐
  159. ties.
  160. DISCLAIMER
  161. Atheros HomePlug AV Vendor Specific Management Message structure and content is proprietary to Qualcomm Atheros, Ocala FL
  162. USA. Consequently, public information may not be available. Qualcomm Atheros reserves the right to modify message
  163. structure and content in future firmware releases without any obligation to notify or compensate users of this program.
  164. EXAMPLES
  165. The following example sets the &quot;time-to-live&quot; property for each channel access priority type: CAP0, CAP1, CAP2, CAP3 and
  166. MME. The property identifier is 101. It needs five 32-bit decimal integer values in microseconds. Data type long spec‐
  167. ifies a 32-bit decimal value that will be converted to little endian format on output.
  168. # plcset -n 101 long 100 long 200 long 250 long 300 long 100
  169. The next example set the User HFID. The first occurance of option -n specifies the property by number as 105. The sec‐
  170. ond occurance specifies the property version as 1. This is merely an example of how to specify the propery version. At
  171. the time of writing, property 105 is still version 0.
  172. # plcset -n 105 -n 1 hfid &quot;Intergalactic Software Pirates&quot;
  173. SEE ALSO
  174. plc(1), getpib(1), modpib(1), plcset(1), setpib(1)
  175. CREDITS
  176. Charles Maier &lt;cmaier@qca.qualcomm.com&gt;
  177. open-plc-utils-0.0.3 Mar 2014 plcset(1)
  178. </pre>
  179. <div class='footerlink'>
  180. [<a href='plcrule.1.html' title=' plcrule.1 '>PREV</a>]
  181. [<a href='toolkit.html' title=' Index '>HOME</a>]
  182. [<a href='plcstat.1.html' title=' plcstat.1 '>NEXT</a>]
  183. </div>
  184. </body>
  185. </html>