Please refer to this topic rgd issue 1)
Also to create some more awareness I contacted "Allwinner Customer Service Team" recently and they made this a Xunlong issue,
their response: " After a short discussion internally, we suggest you contact Xunlong for clarification.
Let's hope for a satisfactory solution, little/ some hope this can be increased as Xunlog is partnering with armbian ... ...
omg, let's bump dev to 5.05 ( current kernel ) and build a fresh debian image.
Mr martinayotte, I should like to express my respect to you for your work!
Will check back later as duty calls ( cooking for the wife ;-) )
hi running armbian ( kernel 4.14 ) and ovpn 2.4.6 and both nanopi neo2 boards.
ovpn is configured with cipher AES-128-CBC and auth SHA256, following results can be seen:
top - 04:53:47 up 26 days, 11:42, 2 users, load average: 0.16, 0.16, 0.09
Tasks: 102 total, 2 running, 57 sleeping, 0 stopped, 0 zombie
%Cpu0 : 1.0 us, 1.0 sy, 0.0 ni, 98.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu1 : 1.0 us, 2.0 sy, 0.0 ni, 97.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu2 : 20.7 us, 30.1 sy, 0.0 ni, 43.5 id, 0.0 wa, 0.0 hi, 5.7 si, 0.0 st
%Cpu3 : 0.3 us, 0.3 sy, 0.0 ni, 99.0 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st
KiB Mem : 494152 total, 128980 free, 92528 used, 272644 buff/cache
KiB Swap: 247072 total, 229664 free, 17408 used. 382416 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1191 root 20 0 10180 6132 5324 R 59.1 1.2 137:16.90 openvpn
and following with single thread " iperf3 -4 -V -c 192.168.10.2 -t 60 -b 0 -P 1 "
also did not tweak kernel settings too much atm - both ends read:
net.core.default_qdisc = fq_codel
net.core.netdev_max_backlog = 1024
net.core.rmem_max = 33554432
net.core.wmem_max = 33554432
net.ipv4.tcp_rmem = 4096 87380 33554432
net.ipv4.tcp_wmem = 4096 87380 33554432
net.ipv4.tcp_congestion_control = bbr # RETEST westwood OR cubic
net.ipv4.tcp_max_syn_backlog = 1024
net.ipv4.tcp_slow_start_after_idle = 0
net.ipv4.tcp_no_metrics_save = 0
net.ipv4.ip_local_port_range = 9000 65535
If you want a cheap and low wattage VPN consider H5 boards ( eg nanopi neo2 or orange pi zero plus2 ) that should handle proper TV streaming (15-20Mbit) over ovpn this is your option.
If speed will be most important consider other platforms, I'm currently looking in to the ASRock J4005B-ITX and should do 300Mbit ...
thanks for clarifying Igor, will RTFM next time better ...
Don't worry will try not to bug too much and build from scratch, as long I can use NanoPi NEO2 crypto engine Id be more than happy ;-)