Add features from OpenWRT

Add features inherited from OpenWRT as well as OLSR Restart and 
screenshot fixes.
This commit is contained in:
Steve Lewis KC0EUW 2020-02-20 08:18:46 -07:00 committed by Joe AE6XE
parent 8f7e3a51a1
commit 249e0da301
6 changed files with 15 additions and 5 deletions

Binary file not shown.

Before

Width:  |  Height:  |  Size: 73 KiB

After

Width:  |  Height:  |  Size: 91 KiB

BIN
arednGettingStarted/_images/05-mesh-status.png Executable file → Normal file

Binary file not shown.

Before

Width:  |  Height:  |  Size: 38 KiB

After

Width:  |  Height:  |  Size: 71 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 81 KiB

After

Width:  |  Height:  |  Size: 88 KiB

View File

@ -270,7 +270,7 @@ The **Advanced Configuration** section allows you to change settings for various
:alt: Advanced Configuration
:align: center
Above the settings table there are links that allow you to 1) view the node help file, 2) reboot the node, or 3) reset the node to a firstboot or "N0CALL" configuration.
Above the settings table there are links that allow you to 1) view the node help file, 2) reboot the node, or 3) reset the node to a firstboot or "NOCALL" configuration.
Specific values can be set for the following items. You may change these settings and then click the *Save Setting* button. You may also reset these items to their default values by clicking the *Set to Default* button.
@ -290,8 +290,10 @@ Specific values can be set for the following items. You may change these setting
Specifies whether Power over Ethernet should be enabled on nodes with ports that support PoE passthrough.
*USB Passthrough*
Specifies whether the USB port should be enabled on nodes having a USB port.
Specifies whether USB power passthrough should be enabled on nodes having a USB port.
*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.
Node Reset Button
-----------------
@ -300,7 +302,7 @@ The reset button on an AREDN |trade| node has two built-in functions based on th
With the node powered on and fully booted:
* **Hold for 5 seconds to reset the password and DHCP server**
* **Hold for 5 seconds to reset the password and DHCP service**
* **Hold for 15 seconds to return the node to “just-flashed” condition**
On some equipment models it may be possible to accomplish these reset procedures by pressing the *Reset* button on the PoE unit.

View File

@ -7,7 +7,7 @@ After you have installed the AREDN |trade| firmware, rebooted the device, and co
----------
.. image:: _images/01-setup-nocall.png
:alt: Setup N0CALL
:alt: Setup NOCALL
:align: center
----------

View File

@ -14,5 +14,13 @@ There are two types of firmware images: one for the first-time replacement of th
Once you have selected the correct firmware image for your device, click the link to download the image file to your local computer. Make a note of the download location on your computer, since you will need to use that image to install the AREDN |trade| firmware on your device.
**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 build 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.
.. |trade| unicode:: U+00AE .. Registered Trademark SIGN
:ltrim: