08-07-2014, 06:06 AM
This is the contents of openvpn.log concerning the phone:
Here is my vpn.cnf:
Server.conf on CentOS:
The OpenVPN peeps are saying " Some packets are exchanged during TLS negotiation and then the far side rejects it and connects again 6 seconds later."
They say logs would help if the blasted phone had some sort of logging!
Okay so what is going on?
Quote:Wed Aug 6 16:54:32 2014 us=313342 192.168.5.133:1024 Re-using SSL/TLS context
Wed Aug 6 16:54:32 2014 us=313771 192.168.5.133:1024 LZO compression initialized
Wed Aug 6 16:54:32 2014 us=318080 192.168.5.133:1024 Control Channel MTU parms [ L:1542 D:138 EF:38 EB:0 ET:0 EL:0 ]
Wed Aug 6 16:54:32 2014 us=318498 192.168.5.133:1024 Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:135 ET:0 EL:0 AF:3/1 ]
Wed Aug 6 16:54:32 2014 us=319522 192.168.5.133:1024 Local Options String: 'V4,dev-type tun,link-mtu 1542,tun-mtu 1500,proto UDPv4,comp-lzo,cipher BF-CBC,auth SHA1,keysize 128,key-method 2,tls-server'
Wed Aug 6 16:54:32 2014 us=319603 192.168.5.133:1024 Expected Remote Options String: 'V4,dev-type tun,link-mtu 1542,tun-mtu 1500,proto UDPv4,comp-lzo,cipher BF-CBC,auth SHA1,keysize 128,key-method 2,tls-client'
Wed Aug 6 16:54:32 2014 us=319867 192.168.5.133:1024 Local Options hash (VER=V4): '530fdded'
Wed Aug 6 16:54:32 2014 us=319932 192.168.5.133:1024 Expected Remote Options hash (VER=V4): '41690919'
RWed Aug 6 16:54:32 2014 us=320869 192.168.5.133:1024 TLS: Initial packet from 192.168.5.133:1024, sid=396cae71 e601aba6
WWRRWWWWRRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWWWWed Aug 6 16:54:38 2014 us=59111 192.168.5.133:1024 write UDPv4 [ECONNREFUSED]: Connection refused (code=111)
WWWed Aug 6 16:54:38 2014 us=64097 read UDPv4 [ECONNREFUSED|ECONNREFUSED]: Connection refused (code=111)
RWed Aug 6 16:54:38 2014 us=448286 192.168.5.133:1024 TLS: new session incoming connection from 192.168.5.133:1024
WRRWWWWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWed Aug 6 16:54:40 2014 us=835859 192.168.5.133:1024 TLS: new session incoming connection from 192.168.5.133:1024
WWWWWWWWWWWWWWWWRWWWWWWWWWWWWWWWWWRWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWRWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWRWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW
Here is my vpn.cnf:
Quote:client
nobind
dev tun
remote 192.168.5.106
proto udp
port 1194
comp-lzo
ca /yealink/config/openvpn/keys/ca.crt
cert /yealink/config/openvpn/keys/client.crt
key /yealink/config/openvpn/keys/client.key
verb 5
Server.conf on CentOS:
Quote:local 192.168.5.106
port 1194
proto udp
dev tun
mode server
ca ca.crt
cert server.crt
key server.key ;This file should be kept secret
dh dh2048.pem
server 10.8.0.0 255.255.255.0
push "explicit-exit-notify 3"
push "dhcp-option DNS 8.8.8.8"
push "dhcp-option DNS 8.8.4.4"
client-to-client
duplicate-cn
keepalive 20 60
persist-key
persist-tun
status openvpn-status.log
log openvpn.log
comp-lzo
verb 5
The OpenVPN peeps are saying " Some packets are exchanged during TLS negotiation and then the far side rejects it and connects again 6 seconds later."
They say logs would help if the blasted phone had some sort of logging!
Okay so what is going on?