Local Alert Messages and Path (#72)
Add local alert message display and path to the documentation.
This commit is contained in:
parent
c007aea305
commit
f81c762a92
Binary file not shown.
After Width: | Height: | Size: 38 KiB |
Binary file not shown.
Before Width: | Height: | Size: 204 KiB After Width: | Height: | Size: 98 KiB |
Binary file not shown.
After Width: | Height: | Size: 6.1 KiB |
Binary file not shown.
Before Width: | Height: | Size: 44 KiB |
Binary file not shown.
After Width: | Height: | Size: 21 KiB |
|
@ -296,7 +296,27 @@ The first several rows in the *Advanced Configuration* table contain the URLs an
|
|||
There is a known intermittent issue that may occur when a node boots. If OLSR fails to propagate information or does not receive all the network hostnames, a one-time restart of OLSR should resolve the issue. OLSR should be restarted on your node if other nodes' *Mesh Status* display have your node's IP address rather than hostname or if "dtdlink" or "mid" is shown in your node's hostname on their *Mesh Status* display. If your node's *Mesh Status* display shows the IP address rather than hostname for a remote node, then that remote node should restart OLSR.
|
||||
|
||||
*AREDN Alert Message (AAM) Refresh*
|
||||
The AREDN |trade| development team may post messages which Internet-connected nodes will automatically retrieve once every 12 hours. You can use this refresh setting if you want your node to retrieve any new messages immediately, without having to wait for the next auto-refresh window.
|
||||
The AREDN |trade| development team may post messages which Internet-connected nodes will automatically retrieve once every 12 hours. You can use this refresh setting if you want your node to retrieve any new messages without having to wait for the next auto-refresh window. Select the *aam refresh* checkbox and click *Save Setting* to trigger an immediate message retrieval.
|
||||
|
||||
*AREDN Alerts Local Path*
|
||||
This field allows you to enter the URL for a local alert message repository. If you configure such a local repository then your nodes without Internet access can also receive alert messages pertinent to your local mesh. As shown below, enter the URL without a trailing backslash.
|
||||
|
||||
.. image:: _images/alertlocalpath.png
|
||||
:alt: Local Alert Message Repository Path
|
||||
:align: center
|
||||
|
||||
A local message repository should be configured on a mesh-connected web server which allows nodes to query the URL you provided. No Internet access is required for this feature to work as designed. You can consult with your local web server administrator in order to obtain the correct URL for the local message repository. Use the following file naming convention on the web server:
|
||||
|
||||
* Create text files for individual nodes by using only lowercase characters with the exact node name, followed by the ``.txt`` extension as shown below.
|
||||
* To create a broadcast message intended for all local nodes, enter your message text in a file named ``all.txt`` using only lowercase characters for the filename.
|
||||
|
||||
.. image:: _images/url-content.png
|
||||
:alt: Local Alert Message Repository Content
|
||||
:align: center
|
||||
|
||||
It is possible to include HTML tags in your message text, such as using the ``<br />`` tag to display subsequent text on the next line. However, it is best practice to keep alert messages short in order to minimize the height of the alert banner displayed on node webpages.
|
||||
|
||||
----------
|
||||
|
||||
Node Reset Button
|
||||
-----------------
|
||||
|
|
|
@ -45,15 +45,17 @@ The **Load Average** is the average number of processes that have been running o
|
|||
|
||||
The :abbr:`OLSR (Optimized Link State Routing protocol)` **Entries** show the total number of entries in the routing table, as well as the number of nodes currently connected to the mesh network.
|
||||
|
||||
Node and Broadcast Messages
|
||||
---------------------------
|
||||
AREDN |trade| Alert Messages
|
||||
----------------------------
|
||||
|
||||
The AREDN |trade| development team now has the ability to post messages which Internet-connected nodes will automatically retrieve once every 12 hours. There are two types of messages: QST/broadcast messages intended for all nodes, and directed messages which are only retrieved by individual nodes. Messages are displayed at the top of the *Node Status* page above the node name. Be aware that there is no guarantee of privacy for these messages, since anyone can view the message repository online.
|
||||
The AREDN |trade| development team has the ability to post messages which Internet-connected nodes will automatically retrieve once every 12 hours. There are two types of messages: QST/broadcast messages intended for all nodes, and directed messages which are only retrieved by individual nodes. Messages are displayed on a node's webpages above the node name. Be aware that there is no guarantee of privacy for these messages, since anyone can view the message repository online.
|
||||
|
||||
.. image:: _images/node-messages.png
|
||||
:alt: Node Message Display
|
||||
.. image:: _images/aam-display.png
|
||||
:alt: AAM Display
|
||||
:align: center
|
||||
|
||||
Regular mesh nodes without Internet access also have the ability to display *Local Alerts*. The process for setting up a local message repository is described in the **Advanced Configuration** section. If a node has Internet access as well as local messages, then both types of messages will be displayed in the AREDN |trade| alerts banner as shown in the example above.
|
||||
|
||||
Signal Charts
|
||||
-------------
|
||||
|
||||
|
|
Loading…
Reference in New Issue