The version is in the system log when you start a server or client.Do both firmwares have the same OpenVPN version? Where can I see which version they have?
Thanks.
The version is in the system log when you start a server or client.
For a detailed response use theDo both firmwares have the same OpenVPN version?
Where can I see which version they have?
openvpn --version
commandopenvpn --version
OpenVPN 2.4.9 arm-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Aug 14 2020
library versions: OpenSSL 1.1.1g 21 Apr 2020, LZO 2.08
Originally developed by James Yonan
Copyright (C) 2002-2018 OpenVPN Inc <sales@openvpn.net>
Compile time defines: enable_async_push=no enable_comp_stub=no enable_crypto=yes enable_crypto_ofb_cfb=yes enable_debug=no enable_def_auth=yes enable_dlopen=unknown enable_dlopen_self=unknown enable_dlopen_self_static=unknown enable_fast_install=yes enable_fragment=yes enable_iproute2=no enable_libtool_lock=yes enable_lz4=yes enable_lzo=yes enable_management=yes enable_multihome=yes enable_pam_dlopen=no enable_pedantic=no enable_pf=yes enable_pkcs11=no enable_plugin_auth_pam=yes enable_plugin_down_root=yes enable_plugins=yes enable_port_share=yes enable_selinux=no enable_server=yes enable_shared=yes enable_shared_with_static_runtimes=no enable_small=no enable_static=yes enable_strict=no enable_strict_options=no enable_systemd=no enable_werror=no enable_win32_dll=yes enable_x509_alt_username=no with_aix_soname=aix with_crypto_library=openssl with_gnu_ld=yes with_mem_check=no with_sysroot=no
openvpn --version
OpenVPN 2.5.0 arm-buildroot-linux-gnueabi [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Nov 29 2020
library versions: OpenSSL 1.1.1h 22 Sep 2020, LZO 2.08
Originally developed by James Yonan
Copyright (C) 2002-2018 OpenVPN Inc <sales@openvpn.net>
Compile time defines: enable_async_push=no enable_comp_stub=no enable_crypto_ofb_cfb=yes enable_debug=no enable_def_auth=yes enable_dlopen=unknown enable_dlopen_self=unknown enable_dlopen_self_static=unknown enable_fast_install=yes enable_fragment=yes enable_iproute2=no enable_libtool_lock=yes enable_lz4=yes enable_lzo=yes enable_management=yes enable_multihome=yes enable_pam_dlopen=no enable_pedantic=no enable_pf=yes enable_pkcs11=no enable_plugin_auth_pam=yes enable_plugin_down_root=yes enable_plugins=yes enable_port_share=yes enable_selinux=no enable_shared=yes enable_shared_with_static_runtimes=no enable_small=no enable_static=yes enable_strict=no enable_strict_options=no enable_systemd=no enable_werror=no enable_win32_dll=yes enable_x509_alt_username=no with_aix_soname=aix with_crypto_library=openssl with_gnu_ld=yes with_mem_check=no with_sysroot=no
For a detailed response use theopenvpn --version
command
e.g. RT-AC68U v384.19
Code:openvpn --version OpenVPN 2.4.9 arm-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Aug 14 2020 library versions: OpenSSL 1.1.1g 21 Apr 2020, LZO 2.08 Originally developed by James Yonan Copyright (C) 2002-2018 OpenVPN Inc <sales@openvpn.net> Compile time defines: enable_async_push=no enable_comp_stub=no enable_crypto=yes enable_crypto_ofb_cfb=yes enable_debug=no enable_def_auth=yes enable_dlopen=unknown enable_dlopen_self=unknown enable_dlopen_self_static=unknown enable_fast_install=yes enable_fragment=yes enable_iproute2=no enable_libtool_lock=yes enable_lz4=yes enable_lzo=yes enable_management=yes enable_multihome=yes enable_pam_dlopen=no enable_pedantic=no enable_pf=yes enable_pkcs11=no enable_plugin_auth_pam=yes enable_plugin_down_root=yes enable_plugins=yes enable_port_share=yes enable_selinux=no enable_server=yes enable_shared=yes enable_shared_with_static_runtimes=no enable_small=no enable_static=yes enable_strict=no enable_strict_options=no enable_systemd=no enable_werror=no enable_win32_dll=yes enable_x509_alt_username=no with_aix_soname=aix with_crypto_library=openssl with_gnu_ld=yes with_mem_check=no with_sysroot=no
RT-AC86U v386.1 Alpha4
Code:openvpn --version OpenVPN 2.5.0 arm-buildroot-linux-gnueabi [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Nov 29 2020 library versions: OpenSSL 1.1.1h 22 Sep 2020, LZO 2.08 Originally developed by James Yonan Copyright (C) 2002-2018 OpenVPN Inc <sales@openvpn.net> Compile time defines: enable_async_push=no enable_comp_stub=no enable_crypto_ofb_cfb=yes enable_debug=no enable_def_auth=yes enable_dlopen=unknown enable_dlopen_self=unknown enable_dlopen_self_static=unknown enable_fast_install=yes enable_fragment=yes enable_iproute2=no enable_libtool_lock=yes enable_lz4=yes enable_lzo=yes enable_management=yes enable_multihome=yes enable_pam_dlopen=no enable_pedantic=no enable_pf=yes enable_pkcs11=no enable_plugin_auth_pam=yes enable_plugin_down_root=yes enable_plugins=yes enable_port_share=yes enable_selinux=no enable_shared=yes enable_shared_with_static_runtimes=no enable_small=no enable_static=yes enable_strict=no enable_strict_options=no enable_systemd=no enable_werror=no enable_win32_dll=yes enable_x509_alt_username=no with_aix_soname=aix with_crypto_library=openssl with_gnu_ld=yes with_mem_check=no with_sysroot=no
MerlinIs the RT-AC86U log for Merlin or stock?
Merlin
Maybe this reference will help you - in summer RMerlin announced he’ll the most probably stop supporting ac87u and ac3200 (version 384.13_10):Do you know if in the past Merlin updates stopped after Asus stopped updating the firmware of older models?
Maybe this reference will help you - in summer RMerlin announced he’ll the most probably stop supporting ac87u and ac3200 (version 384.13_10):
The reason is limited support from Asus.Changelog (388.x) | Asuswrt-Merlin
www.asuswrt-merlin.net
At the same time, Merlin still fully supports ac66u_b1 that was launched, I believe, in 2016. And which remains fully supported by Asus.
All in all, I don’t think you have to worry about support for your ac86u for next couple of years.
Thanks.
What will happen with Merlin for RT-AC86U when Asus stops issuing new firmware for that router (it's already 4 years old)? Will Merlin stop supporting it? If so, does any other opensource firmware support this model?
I'm about to unbox Asus RT-AC86U and need to decide which firmware to use. I have never installed custom firmware on any device before. The only reason I replaced my wired-only router with a wireless router, and this expensive, is because I want to have OpenVPN in the router instead of Windows. I've read this router has some kind of AES accelerator.
What will happen with Merlin for RT-AC86U when Asus stops issuing new firmware for that router (it's already 4 years old)? Will Merlin stop supporting it?
Asuswrt-Merlin is essentially a fork of the original firmware. Once Asus stops supporting a model, it becomes impossible for me to continue supporting it due to the large amount of closed source portions of code in a firmware, which is model-specific. Once Asus's code and my code start drifting apart too much, then those closed source components become incompatible. This is what happened with the RT-AC87U, where Asus was still using 382 code for that model, and my firmware was using 384 code. Those closed source 382 components can no longer be used with 384 code.
True open source firmwares for commercial routers are all dying. Broadcom and Qualcomm are both increasingly closed in regards to driver code, and they both increasingly rely on more proprietary/closed source components to enhance features. In a few years, the only way to have an open sourced firmware on a modern router will be to build your own router based on an X86 or generic ARM platform platform. DD-WRT and Tomato are going nowhere in terms of new model support, and OpenWRT is increasingly getting cornered in terms of model support as well. I don't think there is any open source firmware that supports a Wifi 6 router right now.
I’m mostly concern with having old OpenVPN on my router once Asus stops releasing new firmware. Is there a way for me to copy and paste new OpenVPN code into the firmware of my router when that happens? It has to be really simple, because I don’t know anything about coding.
I don’t know if this is possible, but perhaps a better business idea would be to sell software people can use in their old PCs and turn them into routers.
It's not as simple as just copying newer files on top of the old one unfortunately. You need to do an actual code merge using tools such as "patch" and "diff", and you also have to adjust other areas of the code when there are changes done at the settings level (for instance, you can't just replace 2.4.x code with 2.5.x and expect it to work properly).
To be honest, OpenVPN is pretty solid security-wise. The code received two independent audit a few years ago, and I've seen very little (if any) security fixes in OpenVPN since then. OpenSSL has also gained a lot in terms of security, with the last few security issues being rather esoteric to exploit (i.e. most can't be exploited through an application such as OpenVPN).
If the VPN service is your main worry, then I can suggest running it on another system behind your router. Can be a virtual machine running on an existing PC, for example. Something like CentOS or Ubuntu LTS should at least give you a few years of security update, and after that you can upgrade the whole distro.
That already exists, and many are actually free. OpenSense, pfSense, Sophos XG (their home edition is free), Gargoyle, etc...
. I assume I should then connect other machines to that OpenVPN machine, but how do I make that connection so all data goes through the OpenVPN machine? I tried to share adapter a while back, but couldn’t make it work.
Does Sophos XG also function as a router?
Also, which is easiest to understand for somebody like me, who thinks the ac86u UI is very complicated: Sophos XG, OPNsense or PFsense?
You didn't specify the goal was to route your outbound traffic through a VPN provider rather than getting remote access to your LAN. That's a completely different scenario. You would need your client to use that VPN router as your default gateway.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!