Just a quick update - I tried using the MT300A with firmware as a OpenVPN client device. I was connecting to my home OpenVPN server. The MT300A was connected via an Ethernet cable to a router in a hotel.
The MT300A with firmware 2.27 was unstable and had difficulty connecting and holding an OpenVPN connection. I re-flashed back to the “old” stable 2.264 firmware and everything was then OK.
The 2.27 firmware appears to have introduced problems with the OpenVPN client functionality.
I am really grateful that you support your devices so please take this as constructive feedback !
Most of what your talking about can be done in the standard .ovpn config no?
Port is in the config
User certificates can also go directly into the config
Force DNS maybe not, but you can define push DNS options combined with route all traffic over the VPN
Thanks for the reply - so the the client firmware is the same on 2.27 and 2.264 ?
i was unable to do any thorough checks on the client VPN on 2.27 but it definitely appeared to have problems which did not happen with 2.264. Looking forward to 2.27 becoming stable !
Hi there! Could please let us know how did you do the set up? Where we can find any instruction? I can’t see any instruction on the web interface (AR300M and 2.27 Firmware).
@alzhao thanks for your reply. I was generating the ovpn file as expected but when I try to import it on my client I got the following error (see attached pic). client is a Linux Ubuntu Machine with Network Manager. Any idea?
I would like to connect from a Linux machine (country A) to my home (country B). Do I need two GL.Inet devices to achieve this or is it enough having one GL.Inet router in my home acting as openvpn server?