iwspy.8 2.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111
  1. .\" Jean II - HPLB - 96
  2. .\" iwspy.8
  3. .\"
  4. .TH IWSPY 8 "31 October 1996" "net-tools" "Linux Programmer's Manual"
  5. .\"
  6. .\" NAME part
  7. .\"
  8. .SH NAME
  9. iwspy \- Get wireless statistics from specific nodes
  10. .\"
  11. .\" SYNOPSIS part
  12. .\"
  13. .SH SYNOPSIS
  14. .BI "iwspy [" interface ]
  15. .br
  16. .BI "iwspy " interface " [+] " DNSNAME " | " IPADDR " | " HWADDR " [...]"
  17. .br
  18. .BI "iwspy " interface " off"
  19. .br
  20. .BI "iwspy " interface " setthr " "low high"
  21. .br
  22. .BI "iwspy " interface " getthr"
  23. .\"
  24. .\" DESCRIPTION part
  25. .\"
  26. .SH DESCRIPTION
  27. .B Iwspy
  28. is used to set a list of addresses to monitor in a wireless network
  29. interface and to read back quality of link information for each of
  30. those. This information is the same as the one available in
  31. .I /proc/net/wireless
  32. : quality of the link, signal strength and noise level.
  33. .PP
  34. This information is updated each time a new packet is received, so
  35. each address of the list adds some overhead in the driver.
  36. .PP
  37. Note that this functionality works only for nodes part of the current
  38. wireless cell, you can not monitor Access Points you are not
  39. associated with (you can use Scanning for that) and nodes in other
  40. cells. In Managed mode, in most case packets are relayed by the Access
  41. Point, in this case you will get the signal strength of the Access
  42. Point. For those reasons this functionality is mostly useful in Ad-Hoc
  43. and Master mode.
  44. .\"
  45. .\" PARAMETER part
  46. .\"
  47. .SH PARAMETERS
  48. You may set any number of addresses up to 8.
  49. .TP
  50. .BR DNSNAME " | " IPADDR
  51. Set an IP address, or in some cases a DNS name (using the name
  52. resolver). As the hardware works with hardware addresses,
  53. .B iwspy
  54. will translate this IP address through
  55. .IR ARP .
  56. In some case, this address might not be in the ARP cache and
  57. .B iwspy
  58. will fail. In those case,
  59. .IR ping (8)
  60. this name/address and retry.
  61. .TP
  62. .B HWADDR
  63. Set a hardware (MAC) address (this address is not translated & checked
  64. like the IP one). The address must contain a colon
  65. .RB ( : )
  66. to be recognised as a hardware address.
  67. .TP
  68. .B +
  69. Add the new set of addresses at the end of the current list instead of
  70. replacing it. The address list is unique for each device, so each user
  71. should use this option to avoid conflicts.
  72. .TP
  73. .B off
  74. Remove the current list of addresses and disable the spy functionality
  75. .TP
  76. .B setthr
  77. Set the
  78. .I low
  79. and
  80. .I high
  81. signal strength threshold for the iwspy event (for drivers that
  82. support it).
  83. .br
  84. Every time the signal strength for any of the address monitored
  85. with iwspy goes lower than the low threshold or goes higher than the
  86. high threshold, a Wireless Event will be generated.
  87. .br
  88. This can be used to monitor link outages without having to run iwspy
  89. periodically.
  90. .TP
  91. .B getthr
  92. Retrieve the current
  93. .I low
  94. and
  95. .I high
  96. signal strength threshold for the iwspy event.
  97. \"
  98. .\" FILES part
  99. .\"
  100. .SH FILES
  101. .I /proc/net/wireless
  102. .\"
  103. .\" SEE ALSO part
  104. .\"
  105. .SH SEE ALSO
  106. .BR iwconfig (8),
  107. .BR iwlist (8),
  108. .BR iwevent (8),
  109. .BR iwpriv (8),
  110. .BR wireless (7).