Community discussions

MikroTik App
 
libove
newbie
Topic Author
Posts: 42
Joined: Tue Aug 14, 2012 5:18 pm

Long-closed OpenVPN connections keep holding IP assignments

Tue Oct 09, 2012 6:39 pm

RouterOS 5.5 (yes, I know, it's out of date). I've set up an OpenVPN server:

>/ppp profile print detail
...
1 name="OpenVPN profile1 Jaytest" local-address=ovpn_pool_win01 remote-address=ovpn_pool_win01 use-mpls=default
use-compression=default use-vj-compression=default use-encryption=required only-one=default change-tcp-mss=default
...

> /ip pool print detail
0 name="dhcp_pool2" ranges=192.168.1.32-192.168.1.192 next-pool=dhcp_pool5
1 name="ovpn_pool_linux" ranges=192.168.5.32/27
2 name="ovpn_pool_win02" ranges=192.168.5.69-192.168.5.70 next-pool=ovpn_pool_win03
3 name="ovpn_pool_win01" ranges=192.168.5.65-192.168.5.66 next-pool=ovpn_pool_win02
4 name="ovpn_pool_win05" ranges=192.168.5.81-192.168.5.82 next-pool=ovpn_pool_win06
5 name="ovpn_pool_win04" ranges=192.168.5.77-192.168.5.78 next-pool=ovpn_pool_win05
6 name="ovpn_pool_win03" ranges=192.168.5.73-192.168.5.74 next-pool=ovpn_pool_win04
7 name="ovpn_pool_win07" ranges=192.168.5.89-192.168.5.90
8 name="ovpn_pool_win06" ranges=192.168.5.85-192.168.5.86 next-pool=ovpn_pool_win07
9 name="dhcp_pool5" ranges=192.168.4.2-192.168.4.254

I have this series of /2 pools because of the limitation of the RouterOS implementation of OpenVPN so that every connected Windows OpenVPN client requires its own /2 subnet.

This all works fine. The problem is that when an OpenVPN session terminates, the MikroTik does not release the IP address which that OpenVPN session allocated. For example, right now, my user "jlibove" is not connected at all, but both of the user's previous OpenVPN sessions from the last few days remain:

/ip pool used print
...
<lots of normal internal LAN DHCP leases>
...
ovpn_pool_win01 192.168.5.65 PPP<79.152.177.205> jlibove
ovpn_pool_win01 192.168.5.66 PPP<79.152.177.205> jlibove

This is from an OpenVPN session from several days ago, long since closed. It's possible that the session closed abnormally, but anyway the MikroTik ought to eventually garbage collect these IP addresses back in to the usable pool.

Is this a known bug/ is there a fix? .. or do I need a script (help, please :-) ) to find and clear dead IP assignments from OpenVPN sessions?

Thanks,
Jay
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 6047
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: Long-closed OpenVPN connections keep holding IP assignme

Wed Oct 10, 2012 11:58 am

Please upgrade to latest version. If still pool addresses are not released then contact support.
 
libove
newbie
Topic Author
Posts: 42
Joined: Tue Aug 14, 2012 5:18 pm

Re: Long-closed OpenVPN connections keep holding IP assignme

Thu Oct 11, 2012 6:37 pm

Please upgrade to latest version. If still pool addresses are not released then contact support.
So, you're saying that this is a known issue, which has been fixed (in what specific version update release)?
Thanks,
-Jay
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 6047
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: Long-closed OpenVPN connections keep holding IP assignme

Fri Oct 12, 2012 2:48 pm

I do not remember exactly when it was fixed but there was something about pool addresses not released.

Who is online

Users browsing this forum: Egert143, emulemodes, glat, Google [Bot], grigoris, HaPe and 109 guests