root@OpenWrt:~# iperf3 -s -D && iperf3 -c 127.0.0.1
Connecting to host 127.0.0.1, port 5201
[ 5] local 127.0.0.1 port 48076 connected to 127.0.0.1 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 4.72 GBytes 40.5 Gbits/sec 0 1.56 MBytes
[ 5] 1.00-2.00 sec 4.84 GBytes 41.6 Gbits/sec 0 1.56 MBytes
[ 5] 2.00-3.00 sec 4.84 GBytes 41.6 Gbits/sec 0 1.56 MBytes
[ 5] 3.00-4.00 sec 4.84 GBytes 41.6 Gbits/sec 0 1.56 MBytes
[ 5] 4.00-5.00 sec 4.84 GBytes 41.6 Gbits/sec 0 1.56 MBytes
[ 5] 5.00-6.00 sec 4.84 GBytes 41.6 Gbits/sec 0 1.56 MBytes
[ 5] 6.00-7.00 sec 4.83 GBytes 41.5 Gbits/sec 0 1.56 MBytes
[ 5] 7.00-8.00 sec 4.83 GBytes 41.5 Gbits/sec 0 1.56 MBytes
[ 5] 8.00-9.00 sec 4.83 GBytes 41.5 Gbits/sec 0 1.56 MBytes
[ 5] 9.00-10.00 sec 4.84 GBytes 41.6 Gbits/sec 0 1.56 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 48.3 GBytes 41.5 Gbits/sec 0 sender
[ 5] 0.00-10.00 sec 48.3 GBytes 41.5 Gbits/sec receiver
iperf Done.
root@OpenWrt:~# ubus call system board
{
"kernel": "5.15.164",
"hostname": "OpenWrt",
"system": "Intel(R) Core(TM) i3-4170 CPU @ 3.70GHz",
"model": "Hewlett-Packard HP EliteDesk 800 G1 DM",
"board_name": "hewlett-packard-hp-elitedesk-800-g1-dm",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "23.05-SNAPSHOT",
"revision": "r24041-a07a531329",
"target": "x86/64",
"description": "OpenWrt 23.05-SNAPSHOT r24041-a07a531329"
}
}
root@OpenWrt:~#
This is a recent "BOSGAME P2 Lite", A.K.A. DB19C. The CPU is probably overkill for this DUAL LAN mini PC as an OpenWrt router, especially as these Ethernet interfaces are 1 Gbps only.
root@OpenWrt:~# ubus call system board
{
"kernel": "5.15.167",
"hostname": "OpenWrt",
"system": "12th Gen Intel(R) Core(TM) i5-12600H",
"model": "Bosgame EffiZen Series",
"board_name": "bosgame-effizen-series",
"rootfs_type": "ext4",
"release": {
"distribution": "OpenWrt",
"version": "23.05.5",
"revision": "r24106-10cc5fcd00",
"target": "x86/64",
"description": "OpenWrt 23.05.5 r24106-10cc5fcd00"
}
}
root@OpenWrt:~# iperf3 -s -D && iperf3 -c 127.0.0.1
Connecting to host 127.0.0.1, port 5201
[ 5] local 127.0.0.1 port 52062 connected to 127.0.0.1 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 10.6 GBytes 91.4 Gbits/sec 0 2.12 MBytes
[ 5] 1.00-2.00 sec 10.8 GBytes 92.8 Gbits/sec 0 2.12 MBytes
[ 5] 2.00-3.00 sec 10.7 GBytes 91.7 Gbits/sec 0 2.12 MBytes
[ 5] 3.00-4.00 sec 10.7 GBytes 91.9 Gbits/sec 0 2.12 MBytes
[ 5] 4.00-5.00 sec 10.4 GBytes 89.0 Gbits/sec 0 2.12 MBytes
[ 5] 5.00-6.00 sec 10.2 GBytes 87.7 Gbits/sec 2 2.12 MBytes
[ 5] 6.00-7.00 sec 10.2 GBytes 87.6 Gbits/sec 2 2.12 MBytes
[ 5] 7.00-8.00 sec 10.7 GBytes 91.9 Gbits/sec 0 2.12 MBytes
[ 5] 8.00-9.00 sec 10.7 GBytes 91.5 Gbits/sec 0 2.12 MBytes
[ 5] 9.00-10.00 sec 10.8 GBytes 92.9 Gbits/sec 0 2.12 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 106 GBytes 91.1 Gbits/sec 4 sender
[ 5] 0.00-10.00 sec 106 GBytes 91.1 Gbits/sec receiver
iperf Done.
I'm late to read this, and off topic, but I can't help mention a nice trick for grep with ps, if it's useful to others:
In the ps | grep iperf | grep -v grep command, where the purpose of the second grep is so that the grep process itself is not included in the output - you can accomplish the same using a bracketed expression containing just one letter eg
ps | grep [i]perf or ps | grep iper[f] etc
eg
# ps | grep iperf
10457 root 1400 S iperf3 -s -D
11033 root 1372 S grep iperf
but
# ps | grep [i]perf
10457 root 1400 S iperf3 -s -D
1 Like