Update old release numbers

Update old release numbers in some examples to avoid confusion.
This commit is contained in:
Steve Lewis AB7PA 2020-11-19 14:52:10 -07:00
parent c9056361f8
commit 54fec5583e
2 changed files with 3 additions and 3 deletions

View File

@ -60,10 +60,10 @@ Download the appropriate *factory* file for your device by following the instruc
> bin [Transfer in "binary" mode]
> trace on [Show the transfer in progress]
> put <full path to the firmware file>
[For example, put /temp/aredn-3.19.3.0-ubnt-nano-m-xw-factory.bin]
[For example, put /temp/aredn-<release>-factory.bin]
-----------------------------------
[Windows with command on a single line]
> tftp -i 192.168.1.20 put C:\temp\aredn-3.19.3.0-ubnt-nano-m-xw-factory.bin
> tftp -i 192.168.1.20 put C:\temp\aredn-<release>-factory.bin
The TFTP client should indicate that data is being transferred and eventually completes.

View File

@ -9,7 +9,7 @@ Understand the impact to your network before using iperf. During the test period
Installing iperf and IperfSpeed
-------------------------------
Two packages should be installed on each AREDN |trade| node in order to facilitate testing between nodes. The `iperf3 <http://downloads.arednmesh.org/releases/3/19/3.19.3.0/packages/mips_24kc/base/iperf3_3.5-1AREDN_mips_24kc.ipk>`_ package allows the nodes to function either as an iperf client or server during the test. The `iperfspeed <https://s3.amazonaws.com/aredn/iperfspeed_0.5_all.ipk>`_ package provides a web-based control interface for running network tests between the nodes.
Two packages should be installed on each AREDN |trade| node in order to facilitate testing between nodes. The **iperf3** package allows the nodes to function either as an iperf client or server during the test, and it can be found in the *base* package download section. The `iperfspeed <https://s3.amazonaws.com/aredn/iperfspeed_0.5_all.ipk>`_ package provides a web-based control interface for running network tests between the nodes.
Using IperfSpeed
----------------