Today, we released the next Core Update Testing!
Please help us test this release, and give feedback here or on other channels, to help us stabilise this soon!
Please note that in this Core Update OpenVPN has been updated from the 2.6 branch to the 2.7 branch.
It would be very good to get as large a range of OpenVPN users evaluating this change during the Testing phase so any issues can be identified and fixed before the release.
I just tested OpenVPN on CU 202 Test
- ISO Installation + Restore Backup CU201
OpenVPN (Roadwarrior) is OK for me 
Upgrade from 201 to 202 aarch64.
Everything works fine: VPN (openvpn, wireguard), DNS Firewall, Wlan, etc.
Sounds good!
Great!
Thank you two for testing (:
I just tested the CU202 Development Build: master/9c65846a
On my N100 + RPi4 test machines with keepalived.
- Install X86_64.iso on Intel N100 + aarc64.img on RPi4.
- Restore Backup from my Prod CU201
No upgrade CU202 problems detected.
I installed OpenVpn Community Gui 2.7.4 on PC, updated to .202 and had no problem using OpenVPN as usual. I have very basic config for it but still…thought it could be useful to try and write results here
Had “funny” things with my NanoPi R4S (ARM based) and upgrade to 202:
After reboot no network started, only heartbeat LED was blinking. I gave it some 1/4h before I did a hard shutdown (unplugged power).
After new power up, R4S seemed to boot normally, and I got the web GUI back, but no internet access. DNS failed - checking led to “error”, even with ISP-assigned DNS server . Trying to reach my DSL modem failed as well, although the firewall rule to allow this was shown to be active. Then I tried to shutdown normally, but R4S did only shut down all network, but did not switch off. Heartbeat LED just kept blinking. I waited another 1/4h before I unplugged power again.
In the meantime I already had started my backup ipfire (intel N3160 based), to have access to internet again, because I thought, the problem could be more severe and solving it may last some longer. But when I powered up the R4S for the next time, it started quite normally with all services as set, and even run a shutdown to switch off.
After repowered for the last time upto now, I swapped my local network settings back to the R4S and everything is well. Until next core update?
Just did upgrade to: /master/2026-05-21 13:47:16 +0000-54f3c26b/x86_64
It went without a hitch 
Minimal testing so far …