add spectral view to WiFi Scan section (#175)
* add spectral view to WiFi Scan section * update scan screenshot * eliminate "signal" from spectral view description * include new auto distance Adv Config setting * correct typo * clarify wording
This commit is contained in:
parent
d375b63144
commit
4f262d25db
Binary file not shown.
Before Width: | Height: | Size: 47 KiB After Width: | Height: | Size: 53 KiB |
Binary file not shown.
After Width: | Height: | Size: 196 KiB |
|
@ -498,6 +498,9 @@ Link Quality Manager (LQM) Settings
|
|||
Minimum Distance
|
||||
The minimum distance (in meters) that must exist between nodes in order for a link to be considered for activation. The default value is 0 meters. This value can be increased if you do not want your node to pass traffic with nearby nodes, for example at a tower site with collocated backbone nodes designed to link only with other distant nodes.
|
||||
|
||||
Auto Distance
|
||||
The distance (in meters) to use when the actual distance between nodes cannot be calculated from their GPS coordinates. The default value is zero, which causes the node to use the "Auto Distance" feature discussed in the *Mesh RF* section above.
|
||||
|
||||
Quality Margin
|
||||
The margin above the *Minimum Quality* that must be detected in order for a node to be returned to the active list based on quality. The default value is 1 percent.
|
||||
|
||||
|
|
|
@ -25,7 +25,7 @@ Neighbor Status
|
|||
If you have *Link Quality Manager* (LQM) enabled, you will also see a button which takes you to the **Neighbor Status** display. LQM is enabled/disabled from the **Advanced Configuration** page, and the settings for LQM are described in the **Configuration Deep Dive** section. The basic settings for *Link Quality Manager* are described below. The theory behind its operation is discussed in the AREDN |trade| *Link Quality Manager* section of the **How-To Guide**.
|
||||
|
||||
WiFi Scan
|
||||
Displays a list of other 802.11 signals that your node can see. The 802.11 signals may include Access Points, neighbor nodes, and other mesh networks (foreign ad-hoc networks). WiFi Scan only finds devices on the same channel width as your node is configured to. When installing at a new location, it is best practice to scan on 5, 10, and 20MHz channels to find all 802.11 signals in range. This information will help to pick a channel clear of other interference. When multiple ad-hoc networks are visible (with different SSIDs or channels), the ID of each 802.11 ad-hoc *network* is displayed but not the individual nodes. There is also an automatic scan mode, but running a Wifi Scan continuously is not recommended, particularly if the node is actively routing traffic. The scan is passive, or only listens for other beacons through all channels, and risks loss of data on the assigned channel. Wifi Scan does not transmit probes on every channel in passive mode, thus no risk of interfering with Radar stations on DFS channels, or other unintended transmissions. Multiple attempts of Wifi Scan will be necessary to find all devices in range.
|
||||
Displays a list of other 802.11 signals within range of your node. The 802.11 signals may include Access Points, neighbor nodes, and other mesh networks (foreign ad-hoc networks). WiFi Scan is described in more detail below.
|
||||
|
||||
Setup
|
||||
Navigates to the **Setup** pages for your node. You will need to supply a username and password to access those pages. The username is always ``root``, while the password is the one you set during initial node setup. If the node has not yet been configured, the password is ``hsmm``.
|
||||
|
@ -132,6 +132,21 @@ Status
|
|||
|
||||
The *Neighbor Status* table will be refreshed automatically every minute as LQM evaluates your node's radio links on an ongoing basis. Links whose quality has improved may be activated, while links whose quality has worsened may be blocked. If an existing node link goes offline, it will age out of the list within about an hour. To refresh the neighbor list on demand you can click the **Refresh** button. If you want to return to the *Node Status* display, click the **Quit** button.
|
||||
|
||||
WiFi Scan
|
||||
---------
|
||||
|
||||
**WiFi Scan** initiates a passive scan for Wifi signals that are within range, but it only reports devices on the same channel width as your node. When installing a node at a new location it is best practice to scan on 5, 10, and 20MHz channel widths to find all 802.11 signals in range. This information will help you to pick a channel clear of other interference. When multiple ad-hoc networks are visible (using different SSIDs or channels), the ID of each 802.11 ad-hoc *network* is displayed but not the individual nodes.
|
||||
|
||||
There is also an automatic scan mode, but running a Wifi Scan continuously is not recommended, particularly if the node is actively routing traffic. The scan is passive and only listens for other beacons through all channels, but there is a risk of data loss on the assigned channel. Wifi Scan does not transmit probes on every channel in passive mode, so there is no risk of interfering with Radar stations on DFS channels or other unintended transmissions. Multiple attempts of Wifi Scan may be necessary to find all devices in range.
|
||||
|
||||
Below the scan results there is a Spectral View of RF energy detected during the scan. This may be useful for visualizing a clear channel for your node.
|
||||
|
||||
.. image:: _images/wifi-scan.png
|
||||
:alt: WiFi Scan
|
||||
:align: center
|
||||
|
||||
|
|
||||
|
||||
AREDN |trade| Alert Messages
|
||||
----------------------------
|
||||
|
||||
|
|
Loading…
Reference in New Issue