Surprisingly, there are lot of users still using openvpn. And armv8 crypto extensions isn't just used for OpenVPN.
It's clear that cortexa72 cores will beat the cortexa53 cores easily in terms of raw performance.
Raspberry PI is designed in such a way that it can be applicable in lots of other use-cases. ML,AI, Image Processing, Desktop, etc, IoT. But, in reality, considering a network application, these features are useless as the openwrt system will be running headless.
No, we're discussing your claim that as a 'VPN' router (shadowsocks/wireguard/openvpn) it'll crush the RPi4. It will only do that if you're using openvpn. If you're using either of the other two VPNs you mentioned then it won't be the case. It will also potentially stop being the case with OpenVPN later this year when they release OpenVPN 2.5 with ChaCha20-Poly1305 support for the data channel.
Shadowsocks has a variety of crypto algorithm, AES included. OpenVPN is also AES.
That leaves us with Wireguard, which uses chacha20, and thats actually really good.
But, out of the most commonly used three named above, only two supports TCP. Thats shadowsocks and OpenVPN.
Its also been known that TCP over TCP is a bad idea. But with congestion algorithms like bbr, it isn't true anymore. Most ISP and organisation throttles and even blocks UDP packets. My ISP is known to throttle UDP packets, even on port UDP/53. For users in China, this is more common. Also MPTCP works over TCP, thats another reason.
make defconfig
fatal: Invalid revision range ee53a240ac902dc83209008a2671e7fdcf55957a..HEAD
fatal: Invalid revision range ee53a240ac902dc83209008a2671e7fdcf55957a..f39366626c335ce6e8cb1f7c6a2c220e772d8b83
fatal: Invalid revision range ee53a240ac902dc83209008a2671e7fdcf55957a..HEAD
fatal: Invalid revision range ee53a240ac902dc83209008a2671e7fdcf55957a..f39366626c335ce6e8cb1f7c6a2c220e772d8b83
WARNING: Makefile 'package/feeds/packages/sqm-scripts/Makefile' has a dependency on 'kmod-sched-cake-virtual', which does not exist
#
# configuration written to .config
#
I've got the nanopi for a week and it's been really stable, no crashes or something strange. I think the build its ready for PR.
I found that the nanopi its really hot, i've got the metal case and somehow its okey, its at 40º at idle, but with SQM and other things the nanopi reachs 60º with just a 40% cpu usage... for my real world use its fine, but if one day i upgrade my conecction i dont know what temps its going to reach.
Sqm work even with the following warning " WARNING: Makefile 'package/feeds/packages/sqm-scripts/Makefile' has a dependency on 'kmod-sched-cake-virtual', which doe
s not exist" ?
No, you have to download the latest master and replace the Makefile from package/kernel/kmod-sched-cake-oot to the nanopi source, just after the git clone command.