Update release to 3.20.3.0 (#52)

* Update release to 3.20.3.0

Update release number in screenshots to 3.20.3.0. Include new comment 
field for tunnels.

* Update wording for firmware targets

Update wording for firmware targets.

* Add steps to Firmware Upgrade Tips

Add steps to the Firmware Upgrade Tips section, and include more info in 
the OLSR Restart section.

arednGettingStarted/advanced_config.rst

@@ -213,6 +213,9 @@ Client Node Name
 Client Password
   Enter a complex password that the client node will use to connect to your node over the tunnel. Use only uppercase and lowercase characters and numbers in your password.
 
+Contact Info/Comment (optional)
+  You have the option to enter a line of text which may include the contact information of the person responsible for a the tunnel endpoint. It is a 50 character freeform text field which can contain any other useful identifier or information as needed.
+
 Once these settings are correct, click *Add* to add the new client to the list of authorized tunnel clients. On the right of each entry there is an envelope icon which will automatically open your computer's email program and copy the client settings into a new email which allows you to quickly and easily send credentials to the owners of the client nodes.
 
 To allow a client to connect to your tunnel server, select the **Enabled?** checkbox and click the **Save Changes** button. When a tunnel connection becomes active, the cloud icon at the right of each row will change to indicate that the tunnel is active.
@@ -295,6 +298,8 @@ Specific values can be set for the following items. You may change these setting
 *OLSR Restart*
   The OLSR routing process can be restarted by clicking the checkbox and then clicking the *Save Setting* button. This can be useful when you want your node to rebuild its mesh routing table but you do not want to do a full reboot.
 
+  There is a known intermittent issue that may occur when OLSR starts as 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. You should do this if you see one or more of the following symptoms on the *Mesh Status* display: 1) a node's IP address rather than hostname is shown; 2) "dtdlink" or "mid" is shown in a hostname; 3) other users can but you cannot access a node by its hostname.
+
 Node Reset Button
 -----------------
 

arednGettingStarted/downloading_firmware.rst

@@ -17,9 +17,9 @@ Once you have selected the correct firmware image for your device, click the lin
 **Features Inherited from OpenWRT for New Architectures**
   The latest AREDN |trade| firmware contains features which are inherited from the newest OpenWRT upstream release (19.07). The OpenWRT *Release Notes* describe these new features and can be found here: `OpenWRT 19.07 Release Notes <http://openwrt.org/releases/19.07/start>`_
 
-  One important change is the inclusion of a new *target* for the firmware, labelled "ath79", which is the successor to the existing "ar71xx" target. The OpenWRT team explains the new target here: `ath79 <http://openwrt.org/docs/techref/targets/ath79>`_. Their main goal is to bring the code into a form that will allow all devices to run a standard unpatched Linux kernel. This will greatly reduce the amount of customization required and will streamline the firmware development process.
+  One important change is the inclusion of a new *target* (architecture) for the firmware, labelled "ath79", which is the successor to the existing "ar71xx" target. The OpenWRT team explains the new target here: `ath79 <http://openwrt.org/docs/techref/targets/ath79>`_. Their main goal is to bring the code into a form that will allow all devices to run a standard unpatched Linux kernel. This will greatly reduce the amount of customization required and will streamline the firmware development process.
 
-  You may notice that the AREDN |trade| firmware download page has one or both of these firmware versions for specific devices. Refer to the latest `firmware notes <http://downloads.arednmesh.org/snapshots/trunk/readme.md>`_ in order to ensure you have the correct firmware image for your specific device.
+  Since not all supported devices have been migrated to the new "ath79" target, AREDN |trade| continues to build firmware for both targets. **You should select the latest recommended target image based on the type of hardware on which it will be installed.** Refer to the latest `firmware notes <http://downloads.arednmesh.org/snapshots/trunk/readme.md>`_ in order to ensure you have the correct firmware image for your specific device.
 
 
 .. |trade|  unicode:: U+00AE .. Registered Trademark SIGN

arednHow-toGuides/firmware_upgrade.rst

@@ -2,17 +2,30 @@
 Firmware Upgrade Tips
 =====================
 
-Upgrading an AREDN |trade| node is a straightforward process accomplished using the *Setup > Administration > Firmware Update* feature on the node's web interface. Follow the procedures documented in the **Downloading AREDN Firmware** section to ensure you have the correct firmware version from the AREDN |trade| website to install on your node. The newest firmware versions have a built-in check to verify that the firmware image you selected is appropriate for the device on which you are installing it. Earlier firmware versions (3.16.1.x and 3.18.9.0) do not have these checks, so be sure you selected the correct firmware version for your device before starting the upgrade.
+Upgrading an AREDN |trade| node is a straightforward process accomplished using the *Setup > Administration > Firmware Update* feature on the node's web interface. Follow the procedures documented in the **Downloading AREDN Firmware** section to ensure you have the correct firmware version from the AREDN |trade| website to install on your node
+
+The newest firmware versions have a built-in check to verify that the firmware image you selected is appropriate for the device on which you are installing it. Earlier firmware versions (3.16.1.x and 3.18.9.0) do not have these checks, so be sure you selected the correct firmware version for your device before starting the upgrade.
 
 Here are some "best practice" tips to assist with the firmware upgrade process. These ensure that memory utilization is at its minimum on the node. The upgrade process can fail due to lack of memory, but such a failure will leave the node unchanged on its previous firmware version.
 
-Before starting the firmware upgrade, it may be necessary to stop, disable, or uninstall extra packages such as Meshchat, snmp, and tunneling. The goal of this step is to keep those processes from using RAM memory and to free as much RAM as possible before the upgrade. Rebooting the node will ensure that its RAM utilization is at a minimum.
+**Use a stepped approach to firmware upgrades**
+  For example, if your node is running version 3.18.9.0 you may want to upgrade to version 3.19.3.0 before attempting to apply a newer version.
 
-You may also want to stop node programs or services that are not needed during the upgrade. For example, if you can telnet or ssh to the node and type the command ``wifi down`` you can free the memory used by this driver.
+**Clear the web browser cache**
+  When using a web browser to perform an upgrade, be sure to clear the browser's cache to remove any cached pages remaining from your node's previous firmware version. A clear cache will help to eliminate confusion when displaying node data in the browser.
 
-When using a web browser to perform an upgrade, be sure to clear the browser's cache to remove any cached pages remaining from your node's previous firmware version. A clear cache will help to eliminate confusion when displaying node data in the browser.
+**Free node resources**
+  Before starting the firmware upgrade, it may be necessary to stop, disable, or uninstall extra packages such as Meshchat, snmp, and tunneling. The goal of this step is to keep those processes from using RAM memory and to free as much RAM as possible before the upgrade. Rebooting the node will ensure that its RAM utilization is at a minimum.
 
-Use a stepped approach to firmware upgrades. For example, if your node is running version 3.18.9.0 you should probably upgrade to version 3.19.3.0 before attempting to apply a newer version.
+  You may also want to stop node programs or services that are not needed during the upgrade. For example, if you can telnet or ssh to the node and type the command ``wifi down`` you can free the memory used by this driver.
+
+**Tips for legacy nodes with low memory (32mb)**
+  Legacy equipment with only 32mb of memory will become more difficult to upgrade as the footprint of firmware images continues to grow. Be sure not to use these types of devices at sites which are difficult to access. The sysupgrade process needs around 10mb of free memory to succeed.
+
+  * You may need to try the sysupgrade procedure several times before it succeeds. Be patient and keep trying.
+  * Get everything ready to do the upgrade, then do a fresh reboot of the node and immediately start the sysupgrade process before the node has time to initialize services which use memory.
+  * Use command line access to copy the *sysupgrade.bin* image to the /tmp directory on the node, then run the sysupgrade process manually from the command line on the node. This procedure is described in the *Troubleshooting Tips* section of **Installing AREDN Firmware**.
+  * As a last resort, use the TFTP procedure to load the *factory.bin* firmware image to the node. This procedure is described in the *First Install* sections of **Installing AREDN Firmware**.
 
 
 .. |trade|  unicode:: U+00AE .. Registered Trademark SIGN

conf.py

@@ -24,9 +24,9 @@ copyright = u'2020, AREDN'
 author = u'KC0EUW'
 
 # The short X.Y version
-version = u'3.19.3.0'
+version = u'3.20.3.0'
 # The full version, including alpha/beta/rc tags
-release = u'3.19.3.0'
+release = u'3.20.3.0'
 
 
 # -- General configuration ---------------------------------------------------

index.rst

@@ -6,7 +6,7 @@
 AREDN |trade| Documentation
 ===========================
 
-:Version: 3.19.3.0
+:Version: 3.20.3.0
 
 This documentation set consists of several sections which are shown in the navigation list.