Disconnect Problem

This forum is for general conversation and user-user networking.

Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech

Post Reply
lex.ukraine
OpenVpn Newbie
Posts: 3
Joined: Wed Mar 01, 2017 9:51 am

Disconnect Problem

Post by lex.ukraine » Wed Mar 01, 2017 10:03 am

I'm using OpenVPN client 2.3.14.l601 on Windows Server 2012 R2. Sometimes connect to OpenVPN-server was down.
That's my client config:
=============================================
remote 1.2.3.4 50010
client
dev tap
proto tcp
resolv-retry infinite # this is necessary for DynDNS
nobind
#user nobody
#group nogroup
persist-key
persist-tun
comp-lzo
verb 4
mute 20
verb 4
keepalive 10 120
ca C:\\Progra~1\\OpenVPN\\Keys\\ca.crt
cert C:\\Progra~1\\OpenVPN\\Keys\\user1.crt
key C:\\Progra~1\\OpenVPN\\Keys\\user1.key
==========================================
That's my client logs:
------------------------------------------------------------------------------------------------------------------------------------------
Wed Mar 01 11:42:15 2017 us=441209 SIGUSR1[soft,ping-restart] received, process restarting
Wed Mar 01 11:42:15 2017 us=441209 Restart pause, 5 second(s)
Wed Mar 01 11:42:20 2017 us=441738 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Wed Mar 01 11:42:20 2017 us=441738 Re-using SSL/TLS context
Wed Mar 01 11:42:20 2017 us=441738 LZO compression initialized
Wed Mar 01 11:42:20 2017 us=441738 Control Channel MTU parms [ L:1576 D:1210 EF:40 EB:0 ET:0 EL:3 ]
Wed Mar 01 11:42:20 2017 us=441738 Socket Buffers: R=[65536->65536] S=[65536->65536]
Wed Mar 01 11:42:20 2017 us=441738 Data Channel MTU parms [ L:1576 D:1450 EF:44 EB:143 ET:32 EL:3 AF:3/1 ]
Wed Mar 01 11:42:20 2017 us=441738 Local Options String: 'V4,dev-type tap,link-mtu 1576,tun-mtu 1532,proto TCPv4_CLIENT,comp-lzo,cipher BF-CBC,auth SHA1,keysize 128,key-method 2,tls-client'
Wed Mar 01 11:42:20 2017 us=441738 Expected Remote Options String: 'V4,dev-type tap,link-mtu 1576,tun-mtu 1532,proto TCPv4_SERVER,comp-lzo,cipher BF-CBC,auth SHA1,keysize 128,key-method 2,tls-server'
Wed Mar 01 11:42:20 2017 us=441738 Local Options hash (VER=V4): '31fdf004'
Wed Mar 01 11:42:20 2017 us=441738 Expected Remote Options hash (VER=V4): '3e6d1056'
Wed Mar 01 11:42:20 2017 us=441738 Attempting to establish TCP connection with [AF_INET]1.2.3.4:50010 [nonblock]
Wed Mar 01 11:42:21 2017 us=457470 TCP connection established with [AF_INET]1.2.3.4:50010
Wed Mar 01 11:42:21 2017 us=457470 TCPv4_CLIENT link local: [undef]
Wed Mar 01 11:42:21 2017 us=457470 TCPv4_CLIENT link remote: [AF_INET]1.2.3.4:50010
Wed Mar 01 11:42:21 2017 us=582483 TLS: Initial packet from [AF_INET]1.2.3.4:50010, sid=df868048 6944b763
Wed Mar 01 11:42:24 2017 us=116533 VERIFY OK: depth=1, C=UK, ST=KHM, L=Khm, O=SV Development, OU=SV, CN=Admin, name=SV, emailAddress=oleg_b15@mail.com
Wed Mar 01 11:42:24 2017 us=116533 VERIFY OK: depth=0, C=UK, ST=KHM, L=Khm, O=SV Development, OU=SV, CN=server, name=SV, emailAddress=oleg_b15@mail.com
Wed Mar 01 11:42:25 2017 us=429170 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Mar 01 11:42:25 2017 us=429170 WARNING: INSECURE cipher with block size less than 128 bit (64 bit). This allows attacks like SWEET32. Mitigate by using a --cipher with a larger block size (e.g. AES-256-CBC).
Wed Mar 01 11:42:25 2017 us=429170 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Mar 01 11:42:25 2017 us=429170 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Mar 01 11:42:25 2017 us=429170 WARNING: INSECURE cipher with block size less than 128 bit (64 bit). This allows attacks like SWEET32. Mitigate by using a --cipher with a larger block size (e.g. AES-256-CBC).
Wed Mar 01 11:42:25 2017 us=429170 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Mar 01 11:42:25 2017 us=429170 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Wed Mar 01 11:42:25 2017 us=429170 [server] Peer Connection Initiated with [AF_INET]1.2.3.4:50010
Wed Mar 01 11:42:28 2017 us=232754 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Wed Mar 01 11:42:33 2017 us=521051 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Wed Mar 01 11:42:38 2017 us=646592 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Wed Mar 01 11:42:43 2017 us=178319 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Wed Mar 01 11:42:48 2017 us=960180 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Wed Mar 01 11:42:53 2017 us=885204 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Wed Mar 01 11:42:58 2017 us=110482 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Wed Mar 01 11:43:03 2017 us=427250 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Wed Mar 01 11:43:08 2017 us=662179 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Wed Mar 01 11:43:13 2017 us=726734 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Wed Mar 01 11:43:14 2017 us=711214 PUSH: Received control message: 'PUSH_REPLY,route 192.168.11.0 255.255.255.0,ping 10,ping-restart 120,route 192.168.50.0 255.255.255.0 192.168.11.254,ifconfig 192.168.11.211 255.255.255.0'
Wed Mar 01 11:43:14 2017 us=711214 OPTIONS IMPORT: timers and/or timeouts modified
Wed Mar 01 11:43:14 2017 us=711214 OPTIONS IMPORT: --ifconfig/up options modified
Wed Mar 01 11:43:14 2017 us=711214 OPTIONS IMPORT: route options modified
Wed Mar 01 11:43:14 2017 us=711214 Preserving previous TUN/TAP instance: Ethernet 2
Wed Mar 01 11:43:14 2017 us=711214 Initialization Sequence Completed
Wed Mar 01 11:43:15 2017 us=8119 PUSH: Received control message: 'PUSH_REPLY,route 192.168.11.0 255.255.255.0,ping 10,ping-restart 120,route 192.168.50.0 255.255.255.0 192.168.11.254,ifconfig 192.168.11.211 255.255.255.0'
Wed Mar 01 11:43:15 2017 us=8119 PUSH: Received control message: 'PUSH_REPLY,route 192.168.11.0 255.255.255.0,ping 10,ping-restart 120,route 192.168.50.0 255.255.255.0 192.168.11.254,ifconfig 192.168.11.211 255.255.255.0'
Wed Mar 01 11:43:15 2017 us=101729 PUSH: Received control message: 'PUSH_REPLY,route 192.168.11.0 255.255.255.0,ping 10,ping-restart 120,route 192.168.50.0 255.255.255.0 192.168.11.254,ifconfig 192.168.11.211 255.255.255.0'
Wed Mar 01 11:43:15 2017 us=133133 PUSH: Received control message: 'PUSH_REPLY,route 192.168.11.0 255.255.255.0,ping 10,ping-restart 120,route 192.168.50.0 255.255.255.0 192.168.11.254,ifconfig 192.168.11.211 255.255.255.0'
Wed Mar 01 11:43:15 2017 us=398787 PUSH: Received control message: 'PUSH_REPLY,route 192.168.11.0 255.255.255.0,ping 10,ping-restart 120,route 192.168.50.0 255.255.255.0 192.168.11.254,ifconfig 192.168.11.211 255.255.255.0'
Wed Mar 01 11:43:15 2017 us=664444 PUSH: Received control message: 'PUSH_REPLY,route 192.168.11.0 255.255.255.0,ping 10,ping-restart 120,route 192.168.50.0 255.255.255.0 192.168.11.254,ifconfig 192.168.11.211 255.255.255.0'
Wed Mar 01 11:43:15 2017 us=914470 PUSH: Received control message: 'PUSH_REPLY,route 192.168.11.0 255.255.255.0,ping 10,ping-restart 120,route 192.168.50.0 255.255.255.0 192.168.11.254,ifconfig 192.168.11.211 255.255.255.0'
Wed Mar 01 11:43:15 2017 us=945721 PUSH: Received control message: 'PUSH_REPLY,route 192.168.11.0 255.255.255.0,ping 10,ping-restart 120,route 192.168.50.0 255.255.255.0 192.168.11.254,ifconfig 192.168.11.211 255.255.255.0'
Wed Mar 01 11:43:16 2017 us=211372 PUSH: Received control message: 'PUSH_REPLY,route 192.168.11.0 255.255.255.0,ping 10,ping-restart 120,route 192.168.50.0 255.255.255.0 192.168.11.254,ifconfig 192.168.11.211 255.255.255.0'
------------------------------------------------------------------------------------------------------------------------------------------
May be somebody can advise how I can to solve problem?
Thants a lot.

lex.ukraine
OpenVpn Newbie
Posts: 3
Joined: Wed Mar 01, 2017 9:51 am

Re: Disconnect Problem

Post by lex.ukraine » Wed Mar 01, 2017 10:12 am

In event viewer of Windows server 2012 I see:
=====================================================================
Notification of a fatal error has been created and sent to the remote endpoint. This can lead to rupture of the connection. TLS protocol defined in the code of a Stop error alert
=====================================================================

TinCanTech
OpenVPN Protagonist
Posts: 11137
Joined: Fri Jun 03, 2016 1:17 pm

Re: Disconnect Problem

Post by TinCanTech » Wed Mar 01, 2017 11:44 am

Who owns the server ?

lex.ukraine
OpenVpn Newbie
Posts: 3
Joined: Wed Mar 01, 2017 9:51 am

Re: Disconnect Problem

Post by lex.ukraine » Wed Mar 01, 2017 1:20 pm

The owner of server is external provider. But connects from other OS (windows, freebsd) and other network works fine. I can ask and post logs openvpn-server, if this help.
Thanks

TinCanTech
OpenVPN Protagonist
Posts: 11137
Joined: Fri Jun 03, 2016 1:17 pm

Re: Disconnect Problem

Post by TinCanTech » Wed Mar 01, 2017 1:27 pm

Just report the problem to the server admin.

Post Reply