A Wireguard comparison DB

Hardware Questions and Recommendations
247 
ubus call system board
{
        "kernel": "5.15.164",
        "hostname": "OpenWrt",
        "system": "ARMv8 Processor rev 4",
        "model": "Xiaomi Redmi Router AX6000 (OpenWrt U-Boot layout)",
        "board_name": "xiaomi,redmi-router-ax6000-ubootmod",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "23.05-SNAPSHOT",
                "revision": "r24041-a07a531329",
                "target": "mediatek/filogic",
                "description": "OpenWrt 23.05-SNAPSHOT r24041-a07a531329"
        }
}

root@OpenWrt:/tmp/331/wg-bench-master# ./benchmark.sh
Connecting to host 169.254.200.2, port 5201
[  5] local 169.254.200.1 port 37438 connected to 169.254.200.2 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  98.9 MBytes   828 Mbits/sec    0    615 KBytes
[  5]   1.00-2.00   sec  99.5 MBytes   835 Mbits/sec    0    643 KBytes
[  5]   2.00-3.00   sec   100 MBytes   842 Mbits/sec    0    643 KBytes
[  5]   3.00-4.00   sec  99.1 MBytes   831 Mbits/sec    0    643 KBytes
[  5]   4.00-5.00   sec   100 MBytes   844 Mbits/sec    0    643 KBytes
[  5]   5.00-6.00   sec   100 MBytes   840 Mbits/sec    0    680 KBytes
[  5]   6.00-7.00   sec  99.4 MBytes   834 Mbits/sec    0    680 KBytes
[  5]   7.00-8.00   sec   100 MBytes   841 Mbits/sec    0    680 KBytes
[  5]   8.00-9.00   sec  99.6 MBytes   836 Mbits/sec    0    680 KBytes
[  5]   9.00-10.00  sec   100 MBytes   840 Mbits/sec    0    680 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec   998 MBytes   837 Mbits/sec    0             sender
[  5]   0.00-10.01  sec   996 MBytes   835 Mbits/sec                  receiver

iperf Done.

root@OpenWrt:/tmp/331/wg-bench-master# ./benchmark.sh -R
Connecting to host 169.254.200.2, port 5201
Reverse mode, remote host 169.254.200.2 is sending
[  5] local 169.254.200.1 port 39202 connected to 169.254.200.2 port 5201
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  95.4 MBytes   799 Mbits/sec
[  5]   1.00-2.00   sec  97.0 MBytes   814 Mbits/sec
[  5]   2.00-3.00   sec  95.9 MBytes   804 Mbits/sec
[  5]   3.00-4.00   sec  97.0 MBytes   814 Mbits/sec
[  5]   4.00-5.00   sec  97.0 MBytes   814 Mbits/sec
[  5]   5.00-6.00   sec  96.0 MBytes   805 Mbits/sec
[  5]   6.00-7.00   sec  96.8 MBytes   812 Mbits/sec
[  5]   7.00-8.00   sec  96.5 MBytes   810 Mbits/sec
[  5]   8.00-9.00   sec  96.8 MBytes   811 Mbits/sec
[  5]   9.00-10.00  sec  96.8 MBytes   812 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec   967 MBytes   811 Mbits/sec    0             sender
[  5]   0.00-10.00  sec   965 MBytes   809 Mbits/sec                  receiver

iperf Done.

EDIT: after nft flush ruleset:

root@OpenWrt:/tmp/wg-bench/wg-bench-master#  ./benchmark.sh
Connecting to host 169.254.200.2, port 5201
[  5] local 169.254.200.1 port 37394 connected to 169.254.200.2 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   122 MBytes  1.02 Gbits/sec    0   1.02 MBytes
[  5]   1.00-2.00   sec   118 MBytes   994 Mbits/sec    0   1.13 MBytes
[  5]   2.00-3.00   sec   117 MBytes   979 Mbits/sec    0   1.13 MBytes
[  5]   3.00-4.00   sec   117 MBytes   980 Mbits/sec    0   1.13 MBytes
[  5]   4.00-5.00   sec   118 MBytes   987 Mbits/sec    0   1.13 MBytes
[  5]   5.00-6.00   sec   117 MBytes   982 Mbits/sec    0   1.19 MBytes
[  5]   6.00-7.00   sec   116 MBytes   969 Mbits/sec    0   1.26 MBytes
[  5]   7.00-8.00   sec   117 MBytes   985 Mbits/sec    0   1.26 MBytes
[  5]   8.00-9.00   sec   117 MBytes   982 Mbits/sec    0   1.32 MBytes
[  5]   9.00-10.00  sec   118 MBytes   985 Mbits/sec    0   1.32 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  1.15 GBytes   986 Mbits/sec    0             sender
[  5]   0.00-10.00  sec  1.15 GBytes   984 Mbits/sec                  receiver

iperf Done.
root@OpenWrt:/tmp/wg-bench/wg-bench-master#  ./benchmark.sh -R
Connecting to host 169.254.200.2, port 5201
Reverse mode, remote host 169.254.200.2 is sending
[  5] local 169.254.200.1 port 36874 connected to 169.254.200.2 port 5201
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec   112 MBytes   941 Mbits/sec
[  5]   1.00-2.00   sec   114 MBytes   954 Mbits/sec
[  5]   2.00-3.00   sec   111 MBytes   928 Mbits/sec
[  5]   3.00-4.00   sec   113 MBytes   946 Mbits/sec
[  5]   4.00-5.00   sec   113 MBytes   948 Mbits/sec
[  5]   5.00-6.00   sec   114 MBytes   958 Mbits/sec
[  5]   6.00-7.00   sec   114 MBytes   959 Mbits/sec
[  5]   7.00-8.00   sec   113 MBytes   950 Mbits/sec
[  5]   8.00-9.00   sec   114 MBytes   955 Mbits/sec
[  5]   9.00-10.00  sec   114 MBytes   959 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  1.11 GBytes   953 Mbits/sec    0             sender
[  5]   0.00-10.00  sec  1.11 GBytes   950 Mbits/sec                  receiver

iperf Done.
1 Like
248

May I ask why are you still on 23.05 snapshot but not release?

249

@fakemanhk - I actually went through Attended SysUpgrade. Didn't bother to look for "release" versions. Any reason to go for release channel? More stable?

250

You'll sooner or later run into issues with kernel dependencies, if you attempt to install kmods.

1 Like
251 
{
        "kernel": "5.15.150",
        "hostname": "rt43",
        "system": "ARMv7 Processor rev 5 (v7l)",
        "model": "MikroTik hAP ac2",
        "board_name": "mikrotik,hap-ac2",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "23.05.3",
                "revision": "r23809-234f1a2efa",
                "target": "ipq40xx/mikrotik",
                "description": "OpenWrt 23.05.3 r23809-234f1a2efa"
        }
}

Connecting to host 169.254.200.2, port 5201
[  5] local 169.254.200.1 port 37454 connected to 169.254.200.2 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  16.0 MBytes   134 Mbits/sec    0    194 KBytes       
[  5]   1.00-2.00   sec  16.9 MBytes   142 Mbits/sec    0    194 KBytes       
[  5]   2.00-3.00   sec  17.5 MBytes   147 Mbits/sec    0    214 KBytes       
[  5]   3.00-4.00   sec  16.5 MBytes   139 Mbits/sec    0    224 KBytes       
[  5]   4.00-5.00   sec  12.9 MBytes   108 Mbits/sec    0    263 KBytes       
[  5]   5.00-6.00   sec  15.8 MBytes   132 Mbits/sec    0    263 KBytes       
[  5]   6.00-7.00   sec  17.0 MBytes   143 Mbits/sec    0    301 KBytes       
[  5]   7.00-8.00   sec  17.2 MBytes   145 Mbits/sec    0    317 KBytes       
[  5]   8.00-9.00   sec  17.1 MBytes   144 Mbits/sec    0    317 KBytes       
[  5]   9.00-10.00  sec  16.5 MBytes   138 Mbits/sec    0    317 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec   163 MBytes   137 Mbits/sec    0             sender
[  5]   0.00-10.01  sec   163 MBytes   136 Mbits/sec                  receiver

iperf Done.
1 Like
252

| Turris 1.1 | Freescale P2020 1.2GHz dual core | 2 GiB RAM | 22.03 | 139 Mbits

ubus call system board 
"kernel": "5.15.148",
"hostname": "Turris 1.1",
"system": "e500v2",
"model": "Turris 1.x",
"board_name": "cznic,turris1x",
"rootfs_type": "btrfs",
"release": {
	"distribution": "TurrisOS",
	"version": "7.0.2",
	"revision": "r20343+125",
	"target": "mpc85xx/p2020",
	"description": "TurrisOS 7.0.2"
Reverse mode

./benchmark.sh -R
Connecting to host 169.254.200.2, port 5201
Reverse mode, remote host 169.254.200.2 is sending
[ 5] local 169.254.200.1 port 56802 connected to 169.254.200.2 port 5201
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 15.2 MBytes 128 Mbits/sec
[ 5] 1.00-2.00 sec 15.9 MBytes 133 Mbits/sec
[ 5] 2.00-3.00 sec 16.2 MBytes 136 Mbits/sec
[ 5] 3.00-4.00 sec 16.6 MBytes 139 Mbits/sec
[ 5] 4.00-5.00 sec 16.4 MBytes 137 Mbits/sec
[ 5] 5.00-6.00 sec 16.4 MBytes 137 Mbits/sec
[ 5] 6.00-7.00 sec 16.6 MBytes 140 Mbits/sec
[ 5] 7.00-8.00 sec 16.2 MBytes 136 Mbits/sec
[ 5] 8.00-9.00 sec 16.4 MBytes 137 Mbits/sec
[ 5] 9.00-10.00 sec 16.0 MBytes 134 Mbits/sec

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 166 MBytes 139 Mbits/sec 86 sender
[ 5] 0.00-10.00 sec 162 MBytes 136 Mbits/sec receiver

iperf Done.

noReverse

./benchmark.sh
Connecting to host 169.254.200.2, port 5201
[ 5] local 169.254.200.1 port 33434 connected to 169.254.200.2 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 17.9 MBytes 150 Mbits/sec 0 518 KBytes
[ 5] 1.00-2.00 sec 19.4 MBytes 163 Mbits/sec 0 891 KBytes
[ 5] 2.00-3.00 sec 17.0 MBytes 143 Mbits/sec 0 1.14 MBytes
[ 5] 3.00-4.00 sec 17.4 MBytes 146 Mbits/sec 0 1.28 MBytes
[ 5] 4.00-5.00 sec 17.2 MBytes 144 Mbits/sec 104 1.10 MBytes
[ 5] 5.00-6.00 sec 16.8 MBytes 141 Mbits/sec 0 1.20 MBytes
[ 5] 6.00-7.01 sec 17.2 MBytes 144 Mbits/sec 0 1.20 MBytes
[ 5] 7.01-8.00 sec 17.2 MBytes 145 Mbits/sec 0 1.35 MBytes
[ 5] 8.00-9.00 sec 17.5 MBytes 147 Mbits/sec 22 1.00 MBytes
[ 5] 9.00-10.00 sec 16.6 MBytes 139 Mbits/sec 0 1.06 MBytes

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 174 MBytes 146 Mbits/sec 126 sender
[ 5] 0.00-10.04 sec 171 MBytes 143 Mbits/sec receiver

iperf Done.

253

It appears you are using firmware that is not from the official OpenWrt project.

When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.

You may find that the best options are:

  1. Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
  2. Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
  3. Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).

If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.

254

Not sure this all that relevant here, after all this is about wireguard performance mainly which probably is not all that much affected by the differences between turris and proper OpenWrt, no?...

2 Likes
255

Have no issue with this device - if have one, I'm solving this on different (Turris) forum.

So far have no questions regarding this device so there can't be any 'not useful' advice given.

(Yes - it's fork, don't know how heavily it deviate from OpenWrt - feel free ignore the numbers.)

256

After flashing my now unused router (hope so with proper OpenWrt):

ubus call system board

{
"kernel": "5.15.162",
"hostname": "OpenWrt",
"system": "MediaTek MT7620A ver:2 eco:6",
"model": "Asus RT-AC51U",
"board_name": "asus,rt-ac51u",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "23.05.4",
"revision": "r24012-d8dd03c46f",
"target": "ramips/mt7620",
"description": "OpenWrt 23.05.4 r24012-d8dd03c46f"
}
}

downloaded wg-bench manually as this device does not have enough storage (it fails) and I'm getting this message:

root@OpenWrt:~/wg-bench-master# ./benchmark.sh
iperf3: error - unable to connect to server - server may have stopped running or use a different port, firewall issue, etc.: Connection refused

Attempted to solve it with:

./clean-up.sh 
Cannot find device "wg-bench"

second run print

Cannot remove namespace file "/var/run/netns/wg-bench": No such file or directory
Cannot find device "wg-bench"
Cannot find device "wg-bench-wg"

/etc/init.d/firewall stop

killall iperf3

iperf3 -s -D && iperf3 -c 127.0.0.1

this returning the very same message as if done with ./benchmark.sh

if the ./setup-netns.sh is invoked second time with no clean it does return:

Cannot create namespace file "/var/run/netns/wg-bench": File exists
RTNETLINK answers: File exists
Cannot find device "wg-bench-ns"
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists

and the ./clean-up.sh

Cannot find device "wg-bench"

After clean up it's however possible to run the ./set-up.sh again.

The 'ubus list network.interface.*' does print list

The 'ubus list network.device.*' - Command failed: Not found

So can't do 'service 'device' restart' (reading here) - maybe that could help.

vi /etc/config/network does not show any 'device' other than the 'br-lan'/'eth0.1' being not greyed out in LuCI (but why 'network.device.' - Command failed: Not found*'(?))

Yes - reboot performed.

As this is in /var/run dir, so only persists until reboot - it's somehow outside of configs?

In LuCI after ./clean-up.sh both devices disappear.

Don't know if something can be done with this (and maybe there is mistake I'm doing - apart from choice of weak device).

257

I can understand this, the MT7620A platform devices are pretty much quite weak to handle this.

My tests on Buffalo WCR-1166 and GL-INET MT300Nv1 are pretty much similar and I had to try many rounds, sometimes with reboot and let it settle down a few mins so that I can have it running.

258

I put a remark on OS to indicate it's not an official OpenWrt release, if one day you decided to update to official one you can post another result and let me update.

259

You are right - successfully managed to run couple test (just random attempts..)

after:

root@OpenWrt:~/wg-bench-master# ./benchmark.sh 
iperf3: error - unable to connect to server - server may have stopped running or use a different port, firewall issue, etc.: Connection refused
kill: you need to specify whom to kill

the very next result in:

./benchmark.sh = 21.0 Mbits/sec

root@OpenWrt:~/wg-bench-master# ./benchmark.sh
Connecting to host 169.254.200.2, port 5201
[ 5] local 169.254.200.1 port 47702 connected to 169.254.200.2 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 2.25 MBytes 18.9 Mbits/sec 0 88.2 KBytes
[ 5] 1.00-2.00 sec 2.12 MBytes 17.8 Mbits/sec 0 116 KBytes
[ 5] 2.00-3.00 sec 2.50 MBytes 21.0 Mbits/sec 0 142 KBytes
[ 5] 3.00-4.00 sec 2.50 MBytes 21.0 Mbits/sec 0 142 KBytes
[ 5] 4.00-5.00 sec 2.50 MBytes 21.0 Mbits/sec 0 151 KBytes
[ 5] 5.00-6.00 sec 2.25 MBytes 18.9 Mbits/sec 0 170 KBytes
[ 5] 6.00-7.00 sec 2.38 MBytes 19.9 Mbits/sec 0 170 KBytes
[ 5] 7.00-8.00 sec 2.50 MBytes 21.0 Mbits/sec 0 256 KBytes
[ 5] 8.00-9.00 sec 2.62 MBytes 22.0 Mbits/sec 0 256 KBytes
[ 5] 9.00-10.00 sec 2.62 MBytes 22.0 Mbits/sec 0 256 KBytes

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 24.2 MBytes 20.3 Mbits/sec 0 sender
[ 5] 0.00-10.02 sec 24.0 MBytes 20.1 Mbits/sec receiver

iperf Done.

./benchmark.sh -R = 20.6 Mbits/sec

root@OpenWrt:~/wg-bench-master# ./benchmark.sh -R
Connecting to host 169.254.200.2, port 5201
Reverse mode, remote host 169.254.200.2 is sending
[ 5] local 169.254.200.1 port 42214 connected to 169.254.200.2 port 5201
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 2.25 MBytes 18.8 Mbits/sec
[ 5] 1.00-2.00 sec 2.38 MBytes 19.9 Mbits/sec
[ 5] 2.00-3.00 sec 2.38 MBytes 19.9 Mbits/sec
[ 5] 3.00-4.00 sec 2.50 MBytes 21.0 Mbits/sec
[ 5] 4.00-5.00 sec 2.38 MBytes 19.9 Mbits/sec
[ 5] 5.00-6.00 sec 2.50 MBytes 21.0 Mbits/sec
[ 5] 6.00-7.00 sec 2.38 MBytes 19.9 Mbits/sec
[ 5] 7.00-8.00 sec 2.62 MBytes 22.0 Mbits/sec
[ 5] 8.00-9.00 sec 2.38 MBytes 19.9 Mbits/sec
[ 5] 9.00-10.00 sec 2.50 MBytes 21.0 Mbits/sec

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 24.6 MBytes 20.6 Mbits/sec 0 sender
[ 5] 0.00-10.00 sec 24.2 MBytes 20.3 Mbits/sec receiver

iperf Done.

ubus call system board

root@OpenWrt:~/wg-bench-master# ubus call system board
{
"kernel": "5.15.162",
"hostname": "OpenWrt",
"system": "MediaTek MT7620A ver:2 eco:6",
"model": "Asus RT-AC51U",
"board_name": "asus,rt-ac51u",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "23.05.4",
"revision": "r24012-d8dd03c46f",
"target": "ramips/mt7620",
"description": "OpenWrt 23.05.4 r24012-d8dd03c46f"
}
}

1 Like
260

OK so this result is quite similar to other devices in the same family.
And yeah don't put too much workload on it or it will crash easily (on my MT300Nv1 it might even crash when running AdBlock with a bit more list)

1 Like
261 
root@OpenWrt:~/wg-bench# ./benchmark.sh -R
Connecting to host 169.254.200.2, port 5201
Reverse mode, remote host 169.254.200.2 is sending
[  5] local 169.254.200.1 port 52284 connected to 169.254.200.2 port 5201
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec   396 MBytes  3.31 Gbits/sec
[  5]   1.00-2.00   sec   393 MBytes  3.29 Gbits/sec
[  5]   2.00-3.00   sec   392 MBytes  3.29 Gbits/sec
[  5]   3.00-4.00   sec   396 MBytes  3.32 Gbits/sec
[  5]   4.00-5.00   sec   391 MBytes  3.28 Gbits/sec
[  5]   5.00-6.00   sec   400 MBytes  3.36 Gbits/sec
[  5]   6.00-7.00   sec   398 MBytes  3.34 Gbits/sec
[  5]   7.00-8.00   sec   401 MBytes  3.36 Gbits/sec
[  5]   8.00-9.00   sec   399 MBytes  3.35 Gbits/sec
[  5]   9.00-10.00  sec   397 MBytes  3.33 Gbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  3.87 GBytes  3.33 Gbits/sec    0             sender
[  5]   0.00-10.00  sec  3.87 GBytes  3.32 Gbits/sec                  receiver

iperf Done.
root@OpenWrt:~/wg-bench#

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"
        }
}
262

It's still in 23.05 snapshot?? Not plan to use latest snapshot or official release 23.05.x?

263

Nope, i've run this just for fun, why i should test on lasest snapshot? Is there some interresting change?

264

N100 is performing better with new kernel:


Routers details:
{
        "kernel": "6.6.52",
        "hostname": "DumbAP",
        "system": "Intel(R) N100",
        "model": "Default string Default string",
        "board_name": "default-string-default-string",
        "rootfs_type": "ext4",
        "release": {
                "distribution": "OpenWrt",
                "version": "SNAPSHOT",
                "revision": "r27596-a4c95f1444",
                "target": "x86/64",
                "description": "OpenWrt SNAPSHOT r27596-a4c95f1444"
        }
}
Connecting to host 169.254.200.2, port 4242
[  5] local 169.254.200.1 port 58800 connected to 169.254.200.2 port 4242
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   630 MBytes  5.28 Gbits/sec   58   1.14 MBytes       
[  5]   1.00-2.00   sec   651 MBytes  5.46 Gbits/sec    0   1.45 MBytes       
[  5]   2.00-3.00   sec   653 MBytes  5.47 Gbits/sec   84   1.33 MBytes       
[  5]   3.00-4.00   sec   648 MBytes  5.44 Gbits/sec   54   1.25 MBytes       
[  5]   4.00-5.00   sec   653 MBytes  5.48 Gbits/sec   54   1.16 MBytes       
[  5]   5.00-6.00   sec   655 MBytes  5.49 Gbits/sec    7   1.02 MBytes       
[  5]   6.00-7.00   sec   645 MBytes  5.41 Gbits/sec    0   1.37 MBytes       
[  5]   7.00-8.00   sec   654 MBytes  5.49 Gbits/sec   33   1.21 MBytes       
[  5]   8.00-9.00   sec   653 MBytes  5.47 Gbits/sec   46   1.08 MBytes       
[  5]   9.00-10.00  sec   652 MBytes  5.47 Gbits/sec    0   1.41 MBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  6.34 GBytes  5.45 Gbits/sec  336             sender
[  5]   0.00-10.00  sec  6.34 GBytes  5.44 Gbits/sec                  receiver
2 Likes
265

It uses kernel 6.6 on latest snapshot, looking at other's test on x86 platform seems the Wireguard performance has a significant jump when moving from 5.15 to 6.6.

1 Like
266

Watchguard m300 is source only but here you go.
Will try out my mpc85xx again and upload eventually haha.

{
	"kernel": "6.6.52",
	"hostname": "OpenWrt",
	"system": "e6500, altivec supported",
	"model": "WatchGuard Firebox M300",
	"board_name": "watchguard,firebox-m300",
	"rootfs_type": "initramfs",
	"release": {
		"distribution": "OpenWrt",
		"version": "SNAPSHOT",
		"revision": "r27608+1-3f98f68573",
		"target": "qoriq/generic",
		"description": "OpenWrt SNAPSHOT r27608+1-3f98f68573"
	}
}
Connecting to host 169.254.200.2, port 4242
[  5] local 169.254.200.1 port 54164 connected to 169.254.200.2 port 4242
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  55.6 MBytes   466 Mbits/sec    0    309 KBytes       
[  5]   1.00-2.00   sec  55.2 MBytes   463 Mbits/sec    0    322 KBytes       
[  5]   2.00-3.00   sec  54.1 MBytes   454 Mbits/sec    0    322 KBytes       
[  5]   3.00-4.00   sec  54.0 MBytes   453 Mbits/sec    0    342 KBytes       
[  5]   4.00-5.00   sec  54.9 MBytes   460 Mbits/sec    0    367 KBytes       
[  5]   5.00-6.00   sec  55.0 MBytes   461 Mbits/sec    0    367 KBytes       
[  5]   6.00-7.00   sec  54.4 MBytes   456 Mbits/sec    0    367 KBytes       
[  5]   7.00-8.00   sec  54.5 MBytes   457 Mbits/sec    0    367 KBytes       
[  5]   8.00-9.00   sec  54.8 MBytes   459 Mbits/sec    0    436 KBytes       
[  5]   9.00-10.00  sec  54.6 MBytes   458 Mbits/sec    0    613 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec   547 MBytes   459 Mbits/sec    0             sender
[  5]   0.00-10.00  sec   546 MBytes   458 Mbits/sec                  receiver

iperf Done.
4242/tcp:             5694
1 Like