Actions
Bug #2865
closed
openvpn ping-restart option for TAP interface
Status:
Rejected
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
03/09/2013
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:
Description
If tap interface used other side of the tunnel never will be pinged.
But openvpn server instance by default sends
Mar 9 21:35:51 openvpn[32888]: client1/a.b.c.d:34172 SENT CONTROL [client1]: 'PUSH_REPLY,route a.b.c.d 255.255.255.0,route-gateway a.b.c.d,ping 10,ping-restart 60,ifconfig a.b.c.d 255.255.255.0' (status=1)
As result we have reconnect one a minute
Mar 9 21:38:55 openvpn[32888]: MANAGEMENT: Client connected from /var/etc/openvpn/server1.sock Mar 9 21:38:55 openvpn[32888]: MANAGEMENT: CMD 'status 2' Mar 9 21:38:55 openvpn[32888]: MANAGEMENT: CMD 'quit' Mar 9 21:38:55 openvpn[32888]: MANAGEMENT: Client disconnected Mar 9 21:39:56 openvpn[55675]: MANAGEMENT: Client connected from /var/etc/openvpn/server2.sock Mar 9 21:39:57 openvpn[55675]: MANAGEMENT: CMD 'status 2' Mar 9 21:39:57 openvpn[55675]: MANAGEMENT: CMD 'quit' Mar 9 21:39:57 openvpn[55675]: MANAGEMENT: Client disconnected Mar 9 21:39:57 openvpn[32888]: MANAGEMENT: Client connected from /var/etc/openvpn/server1.sock Mar 9 21:39:57 openvpn[32888]: MANAGEMENT: CMD 'status 2' Mar 9 21:39:57 openvpn[32888]: MANAGEMENT: CMD 'quit' Mar 9 21:39:57 openvpn[32888]: MANAGEMENT: Client disconnected
I guess it could be changed for keepalive and UI option for ping and reinitialization.
Updated by Jim Pingle about 12 years ago
- Status changed from New to Rejected
That disconnect is the management GUI view of the connected clients. It is not disconnecting your actual client.
Reduce your verbosity (which must have been raised from the default) and you won't see those messages.
Actions