newUI-17
This commit is contained in:
ab7pa
parent
fb44b0d1a0
commit
8ce33f1241
|
|
@ -45,7 +45,7 @@ Node Time, Uptime, Load Average, and Free Memory
|
|||
The node time is displayed, as well as the ``uptime``, which is the time since the last reboot. If an Internet connection or a local :abbr:`NTP (Network Time Protocol)` server is available, your node's NTP client will sync its time with that time source. The ``load`` is the average system utilization for the last 1, 5, and 15 minutes. ``free flash`` and ``free ram`` shows how much storage space is remaining on your node. ``flash`` is the internal non-volatile storage where the operating system, configuration files, and software packages are kept. ``ram`` is the amount of :abbr:`RAM (Random Access Memory)` available for running processes on the node.
|
||||
|
||||
Firmware Information
|
||||
This displays the node's current firmware version. A badge on the right indicates the status of the firmware, with valid values including ``Up to date``, ``Update available``, and ``Custom``.
|
||||
This displays the node's current firmware version. A badge on the right indicates the status of the firmware, with valid values including ``Up to date``, ``Update available``, and ``Custom``. If your node has access to the Internet you can also click on the *issues* label below the firmware version, and this will open the AREDN |trade| `Issues <https://github.com/aredn/aredn/issues>`_ page on GitHub. Clicking the *release notes* label will open the `Changelog <https://downloads.arednmesh.org/snapshots/CHANGELOG.md>`_ page on the AREDN |trade| website.
|
||||
|
||||
Network Information
|
||||
The Mesh IP address/netmask is displayed using `CIDR <https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing>`_ notation, followed by the :abbr:`LAN (Local Area Network)` IP address/netmask. If the :abbr:`WAN (Wide Area Network)` interface is enabled, the WAN IP address/netmask is displayed along with whether this address was obtained via `DHCP <https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol>`_ or assigned as a static IP address. The WAN gateway IP address is also displayed along with the IP(s) of the WAN `DNS servers <https://en.wikipedia.org/wiki/Domain_Name_System>`_.
|
||||
|
|
|
|||
|
|
@ -1,49 +0,0 @@
|
|||
==============================
|
||||
Test Network Links with iperf3
|
||||
==============================
|
||||
|
||||
`iperf3 <https://en.wikipedia.org/wiki/Iperf>`_ is an open source network throughput testing tool which is now included in the AREDN |trade| firmware by default. It is a client-server utility, so it must be available on both nodes that participate in the test scenario. The iperf3 client node generates traffic which is sent to the server node. Network throughput is measured and an estimate of the network speeds between that client and server is displayed.
|
||||
|
||||
Understand the impact to your network before using iperf3. During the test period iperf3 will generate a significant amount of traffic in order to determine the capacity of the link between the client and server nodes. Try to run your iperf3 testing during times when you know that there will be minimal impact to the routine traffic between the nodes.
|
||||
|
||||
One of the many uses for iperf3 is to validate and optimize your node's *Distance* setting on the **Basic Setup** page. Try different *Distance* settings and note the network throughput using iperf3, with the goal of choosing a *Distance* setting which yields the best network performance.
|
||||
|
||||
Using the Onboard iperf URL Feature
|
||||
-----------------------------------
|
||||
|
||||
There is a simple, lightweight CGI interface that can be used to run an iperf3 test between two nodes which have firmware with this feature. From any computer connected to the network you can open a new web browser tab or window and type an iperf testing URL having the following format.
|
||||
|
||||
``http://<client_node_name>/cgi-bin/iperf?server=<server_node_name>&protocol=<tcp|udp>``
|
||||
|
||||
*Client Node Name* is the fully qualified node name for the client/sender node. If you do not include the "local.mesh" suffix then it will be added for you.
|
||||
|
||||
*Server Node Name* is the fully qualified node name for the server/receiver node. If you do not include the "local.mesh" suffix then it will be added for you.
|
||||
|
||||
The *Protocol* parameter is optional. If no protocol is specified, then a TCP test will be started. If you want to eliminate the typical TCP handshaking overhead on your network then you can run a connectionless UDP test by adding ``&protocol=udp`` after the server parameter.
|
||||
|
||||
Once you activate the URL in your web browser an iperf3 server will be started on the node you selected as the server, and the client node will initiate the iperf3 test using the protocol you specified (if any). Once the test has completed you will see the collected data summarized by time interval, and at the bottom of the display is the overall average from the perspective of the sender (client) and the receiver (server).
|
||||
|
||||
.. image:: _images/iperfURL.png
|
||||
:alt: iperf URL Display
|
||||
:align: center
|
||||
|
||||
|
|
||||
|
||||
Installing and Using IperfSpeed
|
||||
-------------------------------
|
||||
|
||||
The **IperfSpeed** package provides a web-based control interface for running network tests between nodes, and it was written by Trevor Paskett K7FPV using the Perl programming language. With the project to retire Perl on AREDN |trade| nodes, there is now an alternative *IperfSpeed* package which uses the Lua programming language. The original Perl and new Lua packages are available at the following links:
|
||||
|
||||
- Original Perl version of IperfSpeed [No longer available]
|
||||
|
||||
- `New Lua version of IperfSpeed <https://github.com/kn6plv/iperfspeed>`_
|
||||
|
||||
Select the *IperfSpeed* service on one of the nodes to open its web interface in a new browser tab or window. From the dropdown lists, select a node as the iperf3 server and also one as the iperf3 client. Click the *Run Test* button to begin the network throughput test.
|
||||
|
||||
.. image:: _images/iperfspeed-display.png
|
||||
:alt: iperfSpeed Display
|
||||
:align: center
|
||||
|
||||
|
|
||||
|
||||
Once the test has completed you will see the results displayed in the *IperfSpeed* interface. *IperfSpeed* also tracks previous tests that have been run, and it allows you to rerun any of the previous tests by clicking the *Re-Test* button.
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 150 KiB After Width: | Height: | Size: 20 KiB |
|
|
@ -81,7 +81,6 @@ If you would like to see the documentation for a specific AREDN |trade| release,
|
|||
arednHow-toGuides/poe
|
||||
arednHow-toGuides/lqm
|
||||
arednHow-toGuides/supernodes
|
||||
arednHow-toGuides/iperf
|
||||
arednHow-toGuides/command-line
|
||||
arednHow-toGuides/siso-mimo
|
||||
arednHow-toGuides/radio_mobile_settings
|
||||
|
|
|
|||
Loading…
Reference in New Issue