int6klist.1.html 9.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181
  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. int6klist.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='int6kid.1.html' title=' int6kid.1 '>PREV</a>]
  17. [<a href='toolkit.html' title=' Index '>HOME</a>]
  18. [<a href='int6klog.1.html' title=' int6klog.1 '>NEXT</a>]
  19. </div>
  20. <pre>
  21. int6klist(1) Qualcomm Atheros Open Powerline Toolkit int6klist(1)
  22. NAME
  23. int6klist - List Atheros Device Addresses
  24. SYNOPSIS
  25. int6klist [options] [device] [device] [...]
  26. DESCRIPTION
  27. print the local device address or all network device addresses for a specific device. This program is ideal for that
  28. special script jokey in your life. It only prints device addresses. Nothing else.
  29. Devices are detected using one of two methods. The two methods can be used in combination to determine network topology.
  30. The first method sends one VS_SW_VER message to the Qualcomm Atheros Local Management Address and prints the Ethernet
  31. source address found in each received confirmation message. The method is used when no device addresses appear on the
  32. command line. The result is a list of all local devices, being this connected directly to the local host. Each local
  33. device device may bridge to an independent powerline network having remote devices as members.
  34. The second method sends one VS_NW_INFO message to each specified device and prints the Ethernet source address found in
  35. each received message plus the Ethernet addresses of each network station identified in that message body. This method
  36. is used whenever one, or more, device addresses appear on the command line. It is possible to query remote powerline
  37. devices directly and so duplicate devices addresses are printed when devices share powerline neighbors.
  38. This program is part of the Qualcomm Atheros Powerline Toolkit. See the plc man page for an overview and installation
  39. instructions.
  40. OPTIONS
  41. -b Print bridge device addresses. Each specified device reports it's own address. This option has no effect if no
  42. devices are specified.
  43. -i Select the host Ethernet interface. All requests are sent via this host interface and only reponses received via
  44. this host interface are recognized. The default interface is eth1 because most people use eth0 as their principle
  45. network connection; however, if environment string &quot;PLC&quot; is defined then it takes precedence over the default
  46. interface. This option then takes precedence over either default.
  47. -n Append a newline to output.
  48. -q Enter quiet mode. This option has no effect at this time.
  49. -r Print remote device addresses. Each specified device reports neighbor device addresses. This option has no effect
  50. when no devices are speceified.
  51. -s Insert a newline, instead of a space, between each device address.
  52. -v Enter verbose mode. All Etherenet frames sent or received by the program are displayed on stdout.
  53. -?, --help
  54. Print program help summary on stdout. This option takes precedence over other options on the command line.
  55. -!, --version
  56. Print program version information on stdout. This option takes precedence over other options on the command line.
  57. Use this option when sending screen dumps to Atheros Technical Support so that they know exactly which version of
  58. the Linux Toolkit you are using.
  59. ARGUMENTS
  60. device The MAC address of some powerline device. More than one address may be specified. If omitted the the program out‐
  61. put consists of local device addresses only. Otherwise, output conisists of the specified device followed by all
  62. devices associated with it. The default address is local. See DEVICES for information about symbolic device
  63. addresses.
  64. DEVICES
  65. Powerline devices use Ethernet Media Access Control (MAC) addresses. A MAC address is a 48-bit value entered as 12 hexa‐
  66. decimal digits in upper, lower or mixed character case. Octets may be separated with colons for clarity. For example,
  67. &quot;00b052000001&quot;, &quot;00:b0:52:00:00:01&quot; and &quot;00b052:000001&quot; are valid and equivalent.
  68. The following MAC addresses are special and may be entered by name instead of number.
  69. all Same as &quot;broadcast&quot;.
  70. broadcast
  71. A synonym for the Ethernet broadcast address, FF:FF:FF:FF:FF:FF. All devices, whether local, remote or foreign
  72. recognize messages sent to this address. A remote device is any device at the far end of a powerline connection.
  73. A foreign device is any device not manufactured by Atheros.
  74. local A synonym for the Qualcomm Atheros vendor specific Local Management Address (LMA), 00:B0:52:00:00:01. All local
  75. Atheros devices recognize this address but remote and foreign devices do not. A remote device is any device at the
  76. far end of a powerline connection. A foreign device is any device not manufactured by Atheros.
  77. REFERENCES
  78. See the Qualcomm Atheros HomePlug AV Firmware Technical Reference Manual for more information.
  79. DISCLAIMER
  80. Atheros HomePlug AV Vendor Specific Management Message Entry structure and content is proprietary to Qualcomm Atheros,
  81. Ocala FL USA. Consequently, public information may not be available. Qualcomm Atheros reserves the right to modify mes‐
  82. sage structure and content in future firmware releases without any obligation to notify or compensate users of this pro‐
  83. gram.
  84. EXAMPLES
  85. The following command lists all local devices because no device was specified. Because no devices are specified on the
  86. command line, a VS_SW_VER message is sent to 00:B0:52:00:00:01 and device responses are collected. As we can see, there
  87. is only one local device available at this time. Observe that the prompt appears immediately after the address because
  88. newlines are omitted by default.
  89. # int6klist
  90. 00:B0:52:BE:EF:04 #
  91. The next examples do the same thing but this time there are several local devicer available.
  92. # int6klist
  93. 00:B0:52:BE:EF:04 00:B0:52:BA:BE:02 00:B0:52:BA:BE:01 # int6k
  94. The next example queries the first local device from the previous example, 00:B0:52:BE:EF:04, for a list neighbor
  95. devices. This time a VS_NW_INFO message is sent because we named a device on the command line. The named device happens
  96. to be a local device but it need not be. We can see that the device has no neighbors.
  97. # int6klist 00:B0:52:BE:EF:04
  98. 00:B0:52:BE:EF:04 # int6k
  99. The next example we query the next ocal device, 00:B0:52:BA:BE:02, and find that it has two neighbor devices that did not
  100. show up earlier because they are remote devices. Observe that the three devices comprise a complete logical powerline
  101. network. Device 00:B0:52:BA:BE:02 is connected to the local host but 00:0F:33:F2:01:21 and 00:0f:00:F2:01:13 are con‐
  102. nected to other hosts, somewhere.
  103. # int6klist 00:B0:52:BA:BE:02
  104. 00:B0:52:BA:BE:02 00:0F:33:F2:01:21 00:0F:00:F2:01:13
  105. The next example shows that we can query multiple devices at a time for neighbors. We have copied the output from the
  106. second example and pasted it onto the command line. We now have a list of all devices, local and remote.
  107. # int6klist 00:B0:52:BE:EF:04 00:B0:52:BA:BE:02 00:B0:52:BA:BE:01
  108. 00:B0:52:BE:EF:04 00:B0:52:BA:BE:01 00:B0:52:BA:BE:02 00:0F:33:F2:01:21 00:0F:00:F2:01:13
  109. This next example does the same thing but uses option -n to append a newline after each query. This output is eaiser to
  110. understand because each device queried starts on a new line and is followed by any neighbors.
  111. # int6klist 00:B0:52:BE:EF:04 00:B0:52:BA:BE:02 00:B0:52:BA:BE:01 -n
  112. 00:B0:52:BE:EF:04
  113. 00:B0:52:BA:BE:02 00:0F:33:F2:01:21 00:0F:00:F2:01:13
  114. 00:B0:52:BA:BE:01
  115. This example invokes int6klist which returns a list of local devices. That list is inserted into another int6klist com‐
  116. mand line. This demontrates how program output can be used in scripts.
  117. # int6klist $(int6klist) -n
  118. 00:B0:52:BE:EF:04
  119. 00:B0:52:BA:BE:02 00:0F:33:F2:01:21 00:0F:00:F2:01:13
  120. 00:B0:52:BA:BE:01
  121. This next example accomplishes the same thing since all local device respond with a list of powerline neighbors.
  122. # int6klist local
  123. 00:B0:52:BE:EF:04
  124. 00:B0:52:BA:BE:02 00:0F:33:F2:01:21 00:0F:00:F2:01:13
  125. 00:B0:52:BA:BE:01
  126. SEE ALSO
  127. plc(1), int6krate(1), int6krule(1), int6ktone(1)
  128. CREDITS
  129. Charles Maier &lt;cmaier@qca.qualcomm.com&gt;
  130. open-plc-utils-0.0.3 Mar 2014 int6klist(1)
  131. </pre>
  132. <div class='footerlink'>
  133. [<a href='int6kid.1.html' title=' int6kid.1 '>PREV</a>]
  134. [<a href='toolkit.html' title=' Index '>HOME</a>]
  135. [<a href='int6klog.1.html' title=' int6klog.1 '>NEXT</a>]
  136. </div>
  137. </body>
  138. </html>