pibrump.1.html 5.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114
  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. pibrump.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='pibruin.1.html' title=' pibruin.1 '>PREV</a>]
  17. [<a href='toolkit.html' title=' Index '>HOME</a>]
  18. [<a href='plc.1.html' title=' plc.1 '>NEXT</a>]
  19. </div>
  20. <pre>
  21. pibrump(1) Qualcomm Atheros Open Powerline Toolkit pibrump(1)
  22. NAME
  23. pibrump - Classification Rule Dump Utility
  24. SYNOPSIS
  25. pibrump [options] file [file] [...]
  26. DESCRIPTION
  27. Read classifier rules stored in a PIB file and print them on stdout in a format similar to the command line for program
  28. int6krule. The output can be read by program pibruin for insertion into another PIB file. The program name is short for
  29. &quot;rule dump&quot;.
  30. This program is part of the Qualcomm Atheros Powerline Toolkit. See the AMP man page for an overview and installation
  31. instructions.
  32. OPTIONS
  33. -q Suppresses comments used to group classification rules.
  34. -v Print additional information on stdout. Presently, this option has no effect.
  35. -?,--help
  36. Print program help summary on stdout. This option takes precedence over other options on the command line.
  37. -!,--version
  38. Print program version information on stdout. This option takes precedence over other options on the command line.
  39. Use this option when sending screen dumps to Atheros Technical Support so that they know exactly which version of
  40. the Linux Toolkit you are using.
  41. ARGUMENTS
  42. file The name of a valid Atheros runtime parameter file. The file is not modified by this program. The file must
  43. exist and be a valid runtime parameter file or errors will occur. By convention, runtime parameter files have a
  44. .pib extention but this program does not enforce that convention.
  45. DISCLAIMER
  46. PIB file structure and content is proprietary to Qualcomm Atheros, Ocala FL USA. Consequently, public information is not
  47. available. Qualcomm Atheros reserves the right to change the file structure or content in future firmware releases with‐
  48. out any obligation to notify or compensate users of this program.
  49. EXAMPLES
  50. The following example prints the classifier rules stored in file abc.pib on stdout. Individual rules are printed in a
  51. format that is essentially the same as that used to enter rules using program int6krule. Rules are grouped by their cat‐
  52. egory using comments.
  53. &gt; pibrump abc.pib
  54. # auto connection rules:
  55. StripRX Any VLANID Is 5 VLANID Is 10 VLANID Is 15 add perm
  56. StripRX Any VLANID Is 20 add perm
  57. CAP1 Any VLANID Is 5 VLANID Is 10 VLANID Is 15 add perm
  58. # priority mapping rules:
  59. CAP1 Any VLANID Is 20 add perm
  60. DropRX Any VLANID Is 25 add perm
  61. The next example prints the classifier rules stored in file def.pib but output is a huge disappointment because there are
  62. no rules, much like a Rambo movie.
  63. &gt; pibrump def.pib
  64. # auto connection rules:
  65. # priority mapping rules:
  66. The next example shows a case where the the user has selected two rules from the first example and used them as input to
  67. program int6krule. There is no PIB file involved here because an MME is sent directly to the device with each command
  68. and the device will reset each time. There are times when you may not want to set rules this way.
  69. &gt; int6krule StripRX Any VLANID Is 5 VLANID Is 10 VLANID Is 15 add perm
  70. # int6krule CAP1 Any VLANID Is 20 add perm
  71. The next example reads classification rules from file abc.pib and write them to file rules.txt instead of the console.
  72. The rules are then read from file rules.txt and written into file def.pib using program pibruin. This procedure can be
  73. used to distribute a given rule set to other toolkit users.
  74. &gt; pibrump abc.def &gt; rules.txt
  75. # pibruin &lt; rules.txt def.pib
  76. The next example reads classification rules directly from file abc.pib and writes them directly into file def.pib using
  77. program pibruin.
  78. &gt; pibrump abc.pib | pibruin def.pib
  79. SEE ALSO
  80. int6krule(7), pibruin(7)
  81. CREDITS
  82. Nathaniel Houghton &lt;nhoughto@qca.qualcomm.com&gt;
  83. open-plc-utils-0.0.3 Mar 2014 pibrump(1)
  84. </pre>
  85. <div class='footerlink'>
  86. [<a href='pibruin.1.html' title=' pibruin.1 '>PREV</a>]
  87. [<a href='toolkit.html' title=' Index '>HOME</a>]
  88. [<a href='plc.1.html' title=' plc.1 '>NEXT</a>]
  89. </div>
  90. </body>
  91. </html>