Openvpn connection timing out - > reconnecting; ping-restart

ghurty

Im trying to set up a openvpn - openvpn connection both boxes are 2.0.1-release , but the status on the client shows:
reconnecting; ping-restart 

Here are the logs from the client:
[code
Dec 18 22:11:00 	openvpn[16037]: Inactivity timeout (--ping-restart), restarting
Dec 18 22:11:00 	openvpn[16037]: SIGUSR1[soft,ping-restart] received, process restarting
Dec 18 22:11:02 	openvpn[16037]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Dec 18 22:11:02 	openvpn[16037]: Re-using pre-shared static key
Dec 18 22:11:02 	openvpn[16037]: Preserving previous TUN/TAP instance: ovpnc1
Dec 18 22:11:02 	openvpn[16037]: UDPv4 link local (bound): [AF_INET]YYY.YYY.YYY.YYY
Dec 18 22:11:02 	openvpn[16037]: UDPv4 link remote: [AF_INET]xx.xx.xx.xx:1194
Dec 18 22:12:02 	openvpn[16037]: Inactivity timeout (--ping-restart), restarting
Dec 18 22:12:02 	openvpn[16037]: SIGUSR1[soft,ping-restart] received, process restarting
Dec 18 22:12:04 	openvpn[16037]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Dec 18 22:12:04 	openvpn[16037]: Re-using pre-shared static key
Dec 18 22:12:04 	openvpn[16037]: Preserving previous TUN/TAP instance: ovpnc1
Dec 18 22:12:04 	openvpn[16037]: UDPv4 link local (bound): [AF_INET]YYY.YYY.YYY.YYY
Dec 18 22:12:04 	openvpn[16037]: UDPv4 link remote: [AF_INET]xx.xx.xx.xx:1194
Dec 18 22:13:04 	openvpn[16037]: Inactivity timeout (--ping-restart), restarting
Dec 18 22:13:04 	openvpn[16037]: SIGUSR1[soft,ping-restart] received, process restarting
Dec 18 22:13:06 	openvpn[16037]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Dec 18 22:13:06 	openvpn[16037]: Re-using pre-shared static key
Dec 18 22:13:06 	openvpn[16037]: Preserving previous TUN/TAP instance: ovpnc1
Dec 18 22:13:06 	openvpn[16037]: UDPv4 link local (bound): [AF_INET]YYY.YYY.YYY.YYY
Dec 18 22:13:06 	openvpn[16037]: UDPv4 link remote: [AF_INET]xx.xx.xx.xx:1194

Thanks

cmb

you either have a network connectivity problem or you're trying to connect two clients to the same server instance in a type of config that doesn't support doing so and they're knocking each other offline over and over.

ghurty

Is there a way to rule out the first option?

Thanks

heper

logs should show gateways going offline on either side

jimp

Given that none of those log entries indicate it fully established a connection, I'd say you're either pointing it at the wrong server IP, the firewall rules on the server end are blocking the traffic, or something in between is blocking the traffic.