Reconnect automatically after IP changing

saha66

Hi,

I use valid static IP addresses , and in some cases I have to change the IP address.

The problem is that I have to click the reconnect button or disconnect last connection and connect it again.

Isn't there any solution for solving this problem?

Thanks in advance

saha66

Thanks for your replay,

This is server.conf

port 16080 #- port
proto udp #- protocol
dev tun
tun-mtu 1500
tun-mtu-extra 32
mssfix 1450
reneg-sec 0
no-replay
ca /etc/openvpn/easy-rsa/2.0/keys/ca.crt
cert /etc/openvpn/easy-rsa/2.0/keys/server.crt
key /etc/openvpn/easy-rsa/2.0/keys/server.key
dh /etc/openvpn/easy-rsa/2.0/keys/dh1024.pem
#plugin /etc/openvpn/openvpn-auth-pam.so /etc/pam.d/login
#plugin /etc/openvpn/radiusplugin.so /etc/openvpn/radiusplugin.cnf #- Uncomment this line if you are using FreeRADIUS
#client-cert-not-required
#username-as-common-name
server 10.8.0.0 255.255.255.0
push "redirect-gateway def1"
push "dhcp-option DNS 8.8.8.8"
push "dhcp-option DNS 8.8.4.4"
keepalive 10 60
persist-key
persist-tun
status 1194.log
verb 3

and this is client.conf

client
dev tun
proto udp
remote 123.123.123.123 16080 
resolv-retry 5
nobind
tun-mtu 1500
tun-mtu-extra 32
mssfix 1450
persist-key
persist-tun
ca ca.crt
key client1.key
cert client1.crt
reneg-sec 0
keepalive 10 60
verb 3

Thanks a lot.

saha66

debbie10t wrote As I understand it your server has a fixed public IP address that your clients use all the time to connect to your server.
Your clients IPs change due to DHCP .. is this correct ?

Both (server and client) have fixed public IP address, you know the main problem is that just after the connection start, I will ping the local vpn IP (10.8.0.1) and I get something like below:

Reply from 10.8.0.1: bytes=32 time=326ms TTL=39
Reply from 10.8.0.1: bytes=32 time=302ms TTL=39
Reply from 10.8.0.1: bytes=32 time=331ms TTL=39
Reply from 10.8.0.1: bytes=32 time=309ms TTL=39
Reply from 10.8.0.1: bytes=32 time=311ms TTL=39
Reply from 10.8.0.1: bytes=32 time=326ms TTL=39
Reply from 10.8.0.1: bytes=32 time=302ms TTL=39
Reply from 10.8.0.1: bytes=32 time=331ms TTL=39
Reply from 10.8.0.1: bytes=32 time=309ms TTL=39
Reply from 10.8.0.1: bytes=32 time=311ms TTL=39
Reply from 10.8.0.1: bytes=32 time=326ms TTL=39
Reply from 10.8.0.1: bytes=32 time=302ms TTL=39
Reply from 10.8.0.1: bytes=32 time=331ms TTL=39
Reply from 10.8.0.1: bytes=32 time=309ms TTL=39
Reply from 10.8.0.1: bytes=32 time=311ms TTL=39

but after a while something goes wrong and I get something like below:

Reply from 10.8.0.1: bytes=32 time=326ms TTL=39
Reply from 10.8.0.1: bytes=32 time=302ms TTL=39
Reply from 10.8.0.1: bytes=32 time=331ms TTL=39
Reply from 10.8.0.1: bytes=32 time=309ms TTL=39
Reply from 10.8.0.1: bytes=32 time=311ms TTL=39
Reply from 10.8.0.1: bytes=32 time=326ms TTL=39
Reply from 10.8.0.1: bytes=32 time=302ms TTL=39
Reply from 10.8.0.1: bytes=32 time=331ms TTL=39
Reply from 10.8.0.1: bytes=32 time=309ms TTL=39
Reply from 10.8.0.1: bytes=32 time=311ms TTL=39
Request timed out.
Request timed out.
Reply from 10.8.0.1: bytes=32 time=326ms TTL=39
Reply from 10.8.0.1: bytes=32 time=302ms TTL=39
Reply from 10.8.0.1: bytes=32 time=331ms TTL=39
Reply from 10.8.0.1: bytes=32 time=309ms TTL=39
Reply from 10.8.0.1: bytes=32 time=311ms TTL=39
Reply from 10.8.0.1: bytes=32 time=326ms TTL=39
Reply from 10.8.0.1: bytes=32 time=302ms TTL=39
Reply from 10.8.0.1: bytes=32 time=331ms TTL=39
Reply from 10.8.0.1: bytes=32 time=309ms TTL=39
Reply from 10.8.0.1: bytes=32 time=311ms TTL=39
Request timed out.
Request timed out.
Request timed out.
Reply from 10.8.0.1: bytes=32 time=326ms TTL=39
Reply from 10.8.0.1: bytes=32 time=302ms TTL=39
Reply from 10.8.0.1: bytes=32 time=331ms TTL=39
Reply from 10.8.0.1: bytes=32 time=309ms TTL=39
Reply from 10.8.0.1: bytes=32 time=311ms TTL=39
Reply from 10.8.0.1: bytes=32 time=326ms TTL=39
Reply from 10.8.0.1: bytes=32 time=302ms TTL=39
Reply from 10.8.0.1: bytes=32 time=331ms TTL=39
Reply from 10.8.0.1: bytes=32 time=309ms TTL=39
Reply from 10.8.0.1: bytes=32 time=311ms TTL=39
Request timed out.
Request timed out.

and as soon as I change the fixed public IP address of client and reconnect the openvpn every thing will be ok and after a while (for two or three hours) the result goes wrong.

thanks for your attention

saha66

Of course I can, I just change IP address of client through changing ip address in windows and change it to another public IP address in our subnet, and after that I reconnect openvpn GUI again and every things will be ok.

I mean that after connecting to openvpn for a while the results of pinging none valid IP address of openvpn server (10.8.0.1) would be fine but after two or three hours something goes wrong and the "Request timed out." will increase and quality of my tunnel goes wrong and I have to change the client IP address again.

Excuse me, my english is not good.

saha66

The client version of OpenVPN is:

OpenVPN GUI v1.0.3. A Windows GUI for OpenVPN

And the server version is the last verion of OpenVPN that is running on Centos 6.5.

Whole Client log is as follow:

Wed May 07 20:03:49 2014 OpenVPN 2.1.1 i686-pc-mingw32 [SSL] [LZO2] [PKCS11] built on Dec 11 2009
Wed May 07 20:03:49 2014 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Wed May 07 20:03:49 2014 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Wed May 07 20:03:50 2014 LZO compression initialized
Wed May 07 20:03:50 2014 Control Channel MTU parms [ L:1574 D:138 EF:38 EB:0 ET:0 EL:0 ]
Wed May 07 20:03:50 2014 Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:135 ET:32 EL:0 AF:3/1 ]
Wed May 07 20:03:50 2014 Local Options hash (VER=V4): 'd3a7571a'
Wed May 07 20:03:50 2014 Expected Remote Options hash (VER=V4): '5b1533a2'
Wed May 07 20:03:50 2014 Socket Buffers: R=[8192->8192] S=[8192->8192]
Wed May 07 20:03:50 2014 UDPv4 link local: [undef]
Wed May 07 20:03:50 2014 UDPv4 link remote: 123.123.123.123:53
Wed May 07 20:03:50 2014 TLS: Initial packet from 123.123.123.123:53, sid=fb63d796 ad9e9b45
Wed May 07 20:03:51 2014 VERIFY OK: depth=1, /C=US/ST=CA/L=SanFrancisco/O=Fort-Funston/OU=changeme/CN=CentOS-65-64-minimal/name=changeme/emailAddress=mail@gmail.com
Wed May 07 20:03:51 2014 VERIFY OK: depth=0, /C=US/ST=CA/L=SanFrancisco/O=Fort-Funston/OU=changeme/CN=CentOS-65-64-minimal/name=changeme/emailAddress=mail@gmail.com
Wed May 07 20:03:53 2014 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed May 07 20:03:53 2014 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed May 07 20:03:53 2014 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed May 07 20:03:53 2014 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed May 07 20:03:53 2014 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Wed May 07 20:03:53 2014 [CentOS-65-64-minimal] Peer Connection Initiated with 123.123.123.123:53
Wed May 07 20:03:55 2014 SENT CONTROL [CentOS-65-64-minimal]: 'PUSH_REQUEST' (status=1)
Wed May 07 20:03:55 2014 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 8.8.8.8,dhcp-option DNS 8.8.4.4,route 10.8.0.1,topology net30,ping 5,ping-restart 30,ifconfig 10.8.0.6 10.8.0.5'
Wed May 07 20:03:55 2014 OPTIONS IMPORT: timers and/or timeouts modified
Wed May 07 20:03:55 2014 OPTIONS IMPORT: --ifconfig/up options modified
Wed May 07 20:03:55 2014 OPTIONS IMPORT: route options modified
Wed May 07 20:03:55 2014 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Wed May 07 20:03:55 2014 ROUTE default_gateway=37.254.242.1
Wed May 07 20:03:55 2014 TAP-WIN32 device [Local Area Connection 3] opened: \\.\Global\{379D29D0-A5AA-452D-BD97-FD3C08E72F36}.tap
Wed May 07 20:03:55 2014 TAP-Win32 Driver Version 9.6
Wed May 07 20:03:55 2014 TAP-Win32 MTU=1500
Wed May 07 20:03:55 2014 Notified TAP-Win32 driver to set a DHCP IP/netmask of 10.8.0.6/255.255.255.252 on interface {379D29D0-A5AA-452D-BD97-FD3C08E72F36} [DHCP-serv: 10.8.0.5, lease-time: 31536000]
Wed May 07 20:03:55 2014 Successful ARP Flush on interface [327683] {379D29D0-A5AA-452D-BD97-FD3C08E72F36}
Wed May 07 20:04:01 2014 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Wed May 07 20:04:01 2014 Route: Waiting for TUN/TAP interface to come up...
Wed May 07 20:04:06 2014 TEST ROUTES: 2/2 succeeded len=1 ret=1 a=0 u/d=up
Wed May 07 20:04:06 2014 C:\WINDOWS\system32\route.exe ADD 123.123.123.123 MASK 255.255.255.255 37.254.242.1
Wed May 07 20:04:06 2014 Route addition via IPAPI succeeded [adaptive]
Wed May 07 20:04:06 2014 C:\WINDOWS\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 10.8.0.5
Wed May 07 20:04:06 2014 Route addition via IPAPI succeeded [adaptive]
Wed May 07 20:04:06 2014 C:\WINDOWS\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 10.8.0.5
Wed May 07 20:04:06 2014 Route addition via IPAPI succeeded [adaptive]
Wed May 07 20:04:06 2014 C:\WINDOWS\system32\route.exe ADD 10.8.0.1 MASK 255.255.255.255 10.8.0.5
Wed May 07 20:04:06 2014 Route addition via IPAPI succeeded [adaptive]
Wed May 07 20:04:06 2014 Initialization Sequence Completed
Wed May 07 20:04:38 2014 Replay-window backtrack occurred [1]