Server Side Idle Time Out Configuration
Posted: Wed Nov 10, 2010 7:23 pm
Folks,
After 30 minutes of idle client connection time, I need to have the connection dropped by the server. This would in effect implement a server side idle time out configuration. From the docs, I found --inactive, --ping-exit, and --ping, which as explained, "when used on both peers will cause OpenVPN to exit within 60 seconds if its peer disconnects, but will exit after one hour if no actual tunnel data is exchanged." Apparently 'inactive' is an experimental feature (as of 2.0.6), and may explain why it's not working. I have set in my .conf file as follows:
inactive 1800
ping 10
ping-exit 60
ping-restart 0
The problem I am seeing when adding these lines is that the connection actually disconnects after 60 minutes for Win32 TAP, and constant disconnects and reconnects for TUN users (TunnelBlick/MacOS users).
Thanks
After 30 minutes of idle client connection time, I need to have the connection dropped by the server. This would in effect implement a server side idle time out configuration. From the docs, I found --inactive, --ping-exit, and --ping, which as explained, "when used on both peers will cause OpenVPN to exit within 60 seconds if its peer disconnects, but will exit after one hour if no actual tunnel data is exchanged." Apparently 'inactive' is an experimental feature (as of 2.0.6), and may explain why it's not working. I have set in my .conf file as follows:
inactive 1800
ping 10
ping-exit 60
ping-restart 0
The problem I am seeing when adding these lines is that the connection actually disconnects after 60 minutes for Win32 TAP, and constant disconnects and reconnects for TUN users (TunnelBlick/MacOS users).
Thanks