I think the answer is yes but thought I'd ask.
This can only work with bufferbloat.net domains correct?
I'd love to be able to run against my ISPs server.
I am trying to run this script. The first time I ran it, everything went find and I got a good result. Now when I run it, I always get:
WARNING: netperf returned errors. Results may be inaccurate!
..and I get 0.00 Mbps results.
I can see others above mentioned getting this error as well. How can I see what the error is exactly? Is it possible that I am only allowed to run this script so many times per hour?
With Nanopi R4S and 1Gbps/700Mbps fiber from FREE in France, stock OpenWRT 22.03
# speedtest-netperf.sh -H netperf-eu.bufferbloat.net -p 1.1.1.1 --sequential
2022-09-08 08:28:45 Starting speedtest for 60 seconds per transfer session.
Measure speed to netperf-eu.bufferbloat.net (IPv4) while pinging 1.1.1.1.
Download and upload sessions are sequential, each with 5 simultaneous streams.
.............................................................
Download: 613.39 Mbps
Latency: [in msec, 61 pings, 0.00% packet loss]
Min: 12.030
10pct: 12.312
Median: 12.761
Avg: 12.988
90pct: 13.298
Max: 18.438
CPU Load: [in % busy (avg +/- std dev) @ avg frequency, 56 samples]
cpu0: 21.9 +/- 9.1 @ 915 MHz
cpu1: 19.6 +/- 6.5 @ 940 MHz
cpu2: 20.0 +/- 9.0 @ 733 MHz
cpu3: 16.6 +/- 3.8 @ 586 MHz
cpu4: 58.7 +/- 3.6 @ 584 MHz
cpu5: 14.6 +/- 5.7 @ 581 MHz
Overhead: [in % used of total CPU available]
netperf: 9.8
..............................................................
Upload: 321.73 Mbps
Latency: [in msec, 62 pings, 0.00% packet loss]
Min: 12.041
10pct: 12.614
Median: 13.088
Avg: 13.661
90pct: 14.006
Max: 27.233
CPU Load: [in % busy (avg +/- std dev) @ avg frequency, 58 samples]
cpu0: 24.4 +/- 8.6 @ 759 MHz
cpu1: 5.2 +/- 1.9 @ 806 MHz
cpu2: 12.9 +/- 4.1 @ 882 MHz
cpu3: 4.5 +/- 1.6 @ 712 MHz
cpu4: 33.3 +/- 4.6 @ 408 MHz
cpu5: 17.5 +/- 7.1 @ 438 MHz
Overhead: [in % used of total CPU available]
netperf: 2.0
I've gotten 320Mbps using browser-based speedtest on laptop plugged into router.
Netgear Nighthawk X4S R7800
here's results with speedtest-netperf.sh
root@OpenWrt:/tmp# speedtest-netperf.sh -H netperf-west.bufferbloat.net -p 1.1.1.1 --sequential
2023-01-28 19:42:22 Starting speedtest for 60 seconds per transfer session.
Measure speed to netperf-west.bufferbloat.net (IPv4) while pinging 1.1.1.1.
Download and upload sessions are sequential, each with 5 simultaneous streams.
............................................................
Download: 269.92 Mbps
Latency: [in msec, 61 pings, 0.00% packet loss]
Min: 9.557
10pct: 9.661
Median: 10.111
Avg: 10.626
90pct: 12.925
Max: 14.027
CPU Load: [in % busy (avg +/- std dev) @ avg frequency, 57 samples]
cpu0: 31.4 +/- 5.9 @ 1627 MHz
cpu1: 13.9 +/- 5.7 @ 911 MHz
Overhead: [in % used of total CPU available]
netperf: 19.5
.............................................................
Upload: 286.23 Mbps
Latency: [in msec, 61 pings, 0.00% packet loss]
Min: 9.636
10pct: 10.216
Median: 15.203
Avg: 14.943
90pct: 19.122
Max: 20.214
CPU Load: [in % busy (avg +/- std dev) @ avg frequency, 57 samples]
cpu0: 58.4 +/- 0.0 @ 1725 MHz
cpu1: 6.7 +/- 2.9 @ 779 MHz
Overhead: [in % used of total CPU available]
netperf: 6.2
[ cat /etc/openwrt_release ]
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='22.03.3'
DISTRIB_REVISION='r20028-43d71ad93e'
DISTRIB_TARGET='ipq806x/generic'
DISTRIB_ARCH='arm_cortex-a15_neon-vfpv4'
DISTRIB_DESCRIPTION='OpenWrt 22.03.3 r20028-43d71ad93e'
[ uname -a ]
Linux OpenWrt 5.10.161 #0 SMP Tue Jan 3 00:24:21 2023 armv7l GNU/Linux
Never too late for the solution 
$ mwan3 use wanb command
This will use the specified mwan3 interface. You can use it with ping, with speedtest or with speedtest-netperf.sh
1 Like
I didn't get how to use this command.
Can you give an example?
Do i need to upgrade mwan3 package to use it?
I don't know in what version this was implemented.
The versions I'm using:
mwan3 2.11.7-1
openwrt 22.03.5
Examples:
ping through wan
$ mwan3 use wan ping 8.8.8.8
Speedtest through wanb:
$ mwan3 use wanb speedtest
2 Likes
I see that mwan3 package was upgraded in recent OpenWRT releases.
Must've been this feature added recently.
Either way, good to know such a feature exists.
1 Like