I have noticed after the upgrade of my Linux server, that ovpn client fails to connect to openvpn server 2.1.2, version 2.1.0 is ok. RB411 fails to connect to server and RB433AH hangs partialy. It is unable to list interfaces in WinBox. Console says: Time Out, when tried to list interfaces.

First, I would check the changelog of openvpn server between 2.1.0 -> 2.1.2. Also, in RouterOS, try to turn on debug logging (not sure the exact logging, but debug should work). Then compare the changelog with RouterOS debug messages and check where it's failing, or what might be causing the problem.

Also, it's worth noting that Mikrotik is not investing much time into OpenVPN (and may be removed, just my opinion), so you may wish to try another VPN solution with Mikrotik.

Same here :

I recently updated OVPN server to 2.1.3, i'm no longer able to connect with RouterOS 4.11

OVPN Clients : 2 MT with ROS 4.11 and OVPN V2.1.1 on my laptop
OVPN Server : OVPN V2.1.3 (windows 2008 x64) tried 2.2Beta3 as well, no luck.

Both Mikrotik routers hang up on connection with 100% Cpu usage --> Reboot.
This cause the server side to hang up as well.

My laptop is able to connect with OVPN 2.1.1

I'd like to move to another VPN solution, but how make a L2TP server with Windows 2008 web edition ? :s


Edit : Rolled back to OVPN 2.1.1 for the server -> Working like a charme

I am experiencing this issue as well. ROS 4.12 should better be fixed

I noticed same issue on another site. Result is identical, RB locks and VPN crashes. It is caused by newer version of OpenVPN at server side.

Same here. The problem stil exists in ROS 4.13. RB hangs when ovpn-client tries to connect to a OpenVPN 2.1.x server with x.509-certs.

Same here. The problem stil exists in ROS 4.13. RB hangs when ovpn-client tries to connect to a OpenVPN 2.1.x server with x.509-certs.

Hi all,

same here with ROS 4.12 and 5.0rc5. There are news on this issue? Thankyou!

Hi all,

does anybody solved this issue?
I've the same problem with ROS 5.0rc5 and 3.30.
OpenVPN server version is 2.1.4
With the previous version all was fine..
Thankyou!

It is weird that problem still persist on 5.0rc5 since it should have been fixed in rc4 :

What's new in 5.0rc4 (2010-Nov-22 16:58):

[...]
*) ovpn - make ovpn client work with OpenVPN v2.1.3;
[...]

It is weird that problem still persist on 5.0rc5 since it should have been fixed in rc4 :

What's new in 5.0rc4 (2010-Nov-22 16:58):

[...]
*) ovpn - make ovpn client work with OpenVPN v2.1.3;
[...]

It should work with v2.1.3, but as siugh mentioned:

I've the same problem with ROS 5.0rc5 and 3.30.
OpenVPN server version is 2.1.4
With the previous version all was fine..
Thankyou!

It probably won't work with OpenVPN 2.1.4 (yet), until Mikrotik releases a fix.

Yeah i saw that, but if Mikrotik have to provide a new Ros on each (minor) ovpn version then the problem is not really fixed

Yeah i saw that, but if Mikrotik have to provide a new Ros on each (minor) ovpn version then the problem is not really fixed

I tend to disagree. Basically, the changelog states that it fixes issues with a specific OpenVPN version. If OpenVPN updates to a new release, how is Mikrotik to "magically" work with the new version? The only way is to test against the latest version (Mikrotik + OpenVPN) and for Mikrotik to fix their OS to work with the newer versions of OpenVPN.

Hope this all makes sense

I tend to disagree. Basically, the changelog states that it fixes issues with a specific OpenVPN version. If OpenVPN updates to a new release, how is Mikrotik to "magically" work with the new version? The only way is to test against the latest version (Mikrotik + OpenVPN) and for Mikrotik to fix their OS to work with the newer versions of OpenVPN.

I also tend to disagree.

It is not normal to have a system that almost hangs just because the server side changed to a new version.

If there are changes in the server side that are not compatible with the client side of mikrotik then it just should not connect. Not give 100% load not being able to do practically nothing.

There is no excuse. period.