Steve1985 5 Posted ... I hope someone can help me with the following problem i am facing. I have flashed my router Nighthawk 7800 to the latest (Kong build) dd-wrt firmware. Following this i have followed the exact instructions as on this page: https://airvpn.org/ddwrt/ However when i apply the settings i do see a connection in the air vpn overview for about 2 minutes and then it just drops. In the dd-wrt status it briefly shows a connection and in the log shows as below. I have tried with both UDP and TCP and several ports and servers but all give the same issue. This is making me think there is a setting in dd-wrt that prevents airvpn from functioning. I have performed several factory resets and haven't altered any settings before setting up openvpn following the instructions. During the 2 minutes there is an actual connection my clients are not connected through the VPN despite changing the DNS settings. So this is either part of the same problem or a seperate issue. I am not sure at the moment. Hopefully someone here with more dd-wrt experience can help me out? SteveLogClientlog:20161016 22:41:36 I OpenVPN 2.3.10 arm-unknown-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on May 16 201620161016 22:41:36 I library versions: OpenSSL 1.0.2h 3 May 2016 LZO 2.0920161016 22:41:36 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:1620161016 22:41:36 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts20161016 22:41:36 W WARNING: file '/tmp/openvpncl/client.key' is group or others accessible20161016 22:41:36 W WARNING: file '/tmp/openvpncl/ta.key' is group or others accessible20161016 22:41:36 I Control Channel Authentication: using '/tmp/openvpncl/ta.key' as a OpenVPN static key file20161016 22:41:36 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication20161016 22:41:36 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication20161016 22:41:36 Socket Buffers: R=[87380->87380] S=[16384->16384]20161016 22:41:36 I Attempting to establish TCP connection with [AF_INET]109.232.227.137:443 [nonblock]20161016 22:41:37 I TCP connection established with [AF_INET]109.232.227.137:44320161016 22:41:37 I TCPv4_CLIENT link local: [undef]20161016 22:41:37 I TCPv4_CLIENT link remote: [AF_INET]109.232.227.137:44320161016 22:41:37 TLS: Initial packet from [AF_INET]109.232.227.137:443 sid=54298f20 09cbdd3820161016 22:41:40 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:1620161016 22:41:40 D MANAGEMENT: CMD 'state'20161016 22:41:40 MANAGEMENT: Client disconnected20161016 22:41:40 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:1620161016 22:41:40 D MANAGEMENT: CMD 'state'20161016 22:41:40 MANAGEMENT: Client disconnected20161016 22:41:40 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:1620161016 22:41:40 D MANAGEMENT: CMD 'state'20161016 22:41:40 MANAGEMENT: Client disconnected20161016 22:41:40 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:1620161016 22:41:40 D MANAGEMENT: CMD 'status 2'20161016 22:41:40 MANAGEMENT: Client disconnected20161016 22:41:40 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:1620161016 22:41:40 D MANAGEMENT: CMD 'log 500'19700101 01:00:00ca /tmp/openvpncl/ca.crt cert /tmp/openvpncl/client.crt key /tmp/openvpncl/client.key management 127.0.0.1 16 management-log-cache 100 verb 3 mute 3 syslog writepid /var/run/openvpncl.pid client resolv-retry infinite nobind persist-key persist-tun script-security 2 dev tun1 proto tcp-client cipher aes-256-cbc auth sha1 remote 109.232.227.137 443 comp-lzo yes tls-client tun-mtu 1500 mtu-disc yes ns-cert-type server tun-ipv6 tls-auth /tmp/openvpncl/ta.key 1 tls-cipher TLS-DHE-RSA-WITH-AES-256-GCM-SHA384 Quote Share this post Link to post
go558a83nk 365 Posted ... the line 20161016 22:41:37 TLS: Initial packet from [AF_INET]109.232.227.137:443 sid=54298f20 09cbdd38 is only the beginning of a connection negotiation. The management lines are basically the router showing that it's checking on itself/on the openvpn client. The log you pasted is only showing 3 seconds of time from the initial packet line to where you stopped it. What happens after that? You'll need to show the full log of an actual completed connection (it'll say "initialization sequence completed") and logs of what happens at disconnects. Quote Share this post Link to post