network test package - negan07/ancistrus GitHub Wiki
opkg update && opkg install network-test
Dependencies: none
Files included: network-test.sh, netperf
GUI section: Networking
Nvram variables: none
Docs:
https://github.com/richb-hanover/CeroWrtScripts
https://github.com/guidosarducci/papal-repo
network-test.sh
This script consolidates functionality of the original CeroWrt scripts betterspeedtest.sh and netperfrunner.sh written by Rich Brown:
betterspeedtest.sh (sequential download/upload Speed Test)
netperfrunner.sh (concurrent download/upload Stress Test)
with the internal usage of included Netperf package.
This network-test.sh script merges both scripts above and allows selection of either sequential or concurrent upload and download tests.
It also measures processor usage while testing to help identify being CPU-bound.
Usage
network-test.sh [ -s | -c ] [ -i ] [-4 -6] [ -H netperf-server ] [ -t duration ] [ -p host-to-ping ] [ -n simultaneous-streams ]
Options (if present):
-s | -c: Sequential or concurrent download/upload (default: sequential)
-i | --idle: Don't send traffic, only measure idle latency
-H | --host: DNS or IP address of a netperf server (default: netperf.bufferbloat.net)
-4 | -6: Enable ipv4 or ipv6 testing (default: ipv4)
-t | --time: Test duration time on each direction (default: 60 seconds)
-p | --ping: Host to ping for latency measurements (default: gstatic.com)
-n | --number: Number of simultaneous up/dl sessions (default: 5 sessions)
Select Network Test to Run
Speed Test
Script to simulate http://speedtest.net.
Start pinging, then initiate a download, let it finish, then start an upload.
Output the measured transfer rates and the resulting ping latency.
It's better than speedtest.net because it measures latency while measuring the speed.
Stress Test
It is a shell script that runs several netperf commands simultaneously.
This mimics the stress test of Flent formerly netperf-wrapper .
Starting this script, it concurrently uploads and downloads multiple streams (files) to a server on the Internet.
This places a heavy load on the bottleneck link of the network (Internet connection).
It also starts a ping to a well-connected host.
It displays:
a) total bandwidth available;
b) the distribution of ping latency;
c) the CPU load;
Latency Test
Just idle ping latency and cpu load measurement tests.
It displays:
a) the distribution of ping latency;
b) the CPU load;
Remote Server Hostname
DNS or IP address of a netperf server (default: netperf.bufferbloat.net).
Alternate servers are netperf-east (east coast US), netperf-west (California) and netperf-eu (Denmark).
IP Version
Enable ipv4 or ipv6 testing (default: ipv4). Note that if ipv6 is disabled from related GUI page its option cannot be selected.
Remote Ping Hostname
Host to ping for latency measurements (default: gstatic.com).
Duration
Test duration time on each dl/ul direction (default: 60 seconds).