I suppose you're using UDP. This happens because UDP is stateless protocol and server can't understand if the client disconnected right away unlike TCP. OpenVPN supports special disconnect command which would probably solve your problem
Add the following line in your client config: explicit-exit-notify On 26.09.2015 14:08, Nikolaos Milas wrote: > Hello, > > I am using OpenVPN Server 2.3.5 on CentOS 6.7 x86_64. > > It works fine, but I am having a problem: > > When a client disconnects (mostly using OpenVPN GUI on Win Vista and > later versions, up to Win 10), the OpenVPN server delays to "understand" > the disconnect and consequently delays to run the client-disconnect script. > > Is there a way to resolve this situation? Why the server does not > directly disconnect the client and run the client-disconnect script? > > We need to run the client-disconnect script as soon as possible after > disconnect to release the associated public IP Address and correctly > manage available public IP Addresses. > > Please advise. > > Thanks, > Nick > > > ------------------------------------------------------------------------------ > _______________________________________________ > Openvpn-users mailing list > Openvpn-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openvpn-users
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------
_______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
