Jump to content
Not connected, Your IP: 18.205.60.226
Sign in to follow this  
YLwpLUbcf77U

ANSWERED DD-WRT was working but suddenly stopped

Recommended Posts

I had AirVPN working on my Netgear N7000 with DD-WRT and it suddenly stopped about an hour ago.

 

I am checking the logs and see this:

 

"Clientlog:
19700101 01:04:08 I OpenVPN 2.3.8 arm-unknown-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on Jan 15 2016
19700101 01:04:08 I library versions: OpenSSL 1.0.2e 3 Dec 2015 LZO 2.09
19700101 01:04:08 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:16
19700101 01:04:08 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
19700101 01:04:08 W WARNING: file '/tmp/openvpncl/client.key' is group or others accessible
19700101 01:04:08 W WARNING: file '/tmp/openvpncl/ta.key' is group or others accessible
19700101 01:04:08 I Control Channel Authentication: using '/tmp/openvpncl/ta.key' as a OpenVPN static key file
19700101 01:04:08 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
19700101 01:04:08 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
19700101 01:04:08 Socket Buffers: R=[180224->131072] S=[180224->131072]
19700101 01:04:08 I UDPv4 link local: [undef]
19700101 01:04:08 I UDPv4 link remote: [AF_INET]199.241.146.178:443
19700101 01:04:08 TLS: Initial packet from [AF_INET]199.241.146.178:443 sid=fedc5a85 375a1890
19700101 01:04:09 N VERIFY ERROR: depth=1 error=certificate is not yet valid: C=IT ST=IT L=Perugia O=airvpn.org CN=airvpn.org CA emailAddress=info@airvpn.org
19700101 01:04:09 N TLS_ERROR: BIO read tls_read_plaintext error: error:14090086:lib(20):func(144):reason(134)
19700101 01:04:09 N TLS Error: TLS object -> incoming plaintext read error
19700101 01:04:09 NOTE: --mute triggered...
19700101 01:04:09 1 variation(s) on previous 3 message(s) suppressed by --mute
19700101 01:04:09 I SIGUSR1[soft tls-error] received process restarting
19700101 01:04:09 Restart pause 2 second(s)
19700101 01:04:10 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19700101 01:04:10 D MANAGEMENT: CMD 'state'
19700101 01:04:10 MANAGEMENT: Client disconnected
19700101 01:04:10 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19700101 01:04:10 D MANAGEMENT: CMD 'state'
19700101 01:04:10 MANAGEMENT: Client disconnected
19700101 01:04:10 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19700101 01:04:10 D MANAGEMENT: CMD 'state'
19700101 01:04:10 MANAGEMENT: Client disconnected
19700101 01:04:10 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19700101 01:04:10 D MANAGEMENT: CMD 'status 2'
19700101 01:04:10 MANAGEMENT: Client disconnected
19700101 01:04:10 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19700101 01:04:10 D MANAGEMENT: CMD 'log 500'
19700101 01:04:10 MANAGEMENT: Client disconnected
19700101 01:04:11 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19700101 01:04:11 D MANAGEMENT: CMD 'state'
19700101 01:04:11 MANAGEMENT: Client disconnected
19700101 01:04:11 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19700101 01:04:11 D MANAGEMENT: CMD 'state'
19700101 01:04:11 MANAGEMENT: Client disconnected
19700101 01:04:11 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19700101 01:04:11 D MANAGEMENT: CMD 'state'
19700101 01:04:11 MANAGEMENT: Client disconnected
19700101 01:04:11 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19700101 01:04:11 D MANAGEMENT: CMD 'status 2'
19700101 01:04:11 MANAGEMENT: Client disconnected
19700101 01:04:11 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19700101 01:04:11 D MANAGEMENT: CMD 'log 500'
19700101 01:04:11 MANAGEMENT: Client disconnected
19700101 01:04:12 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19700101 01:04:12 D MANAGEMENT: CMD 'state'
19700101 01:04:12 MANAGEMENT: Client disconnected
19700101 01:04:12 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19700101 01:04:12 D MANAGEMENT: CMD 'state'
19700101 01:04:12 MANAGEMENT: Client disconnected
19700101 01:04:12 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19700101 01:04:12 D MANAGEMENT: CMD 'state'
19700101 01:04:12 MANAGEMENT: Client disconnected
19700101 01:04:12 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19700101 01:04:12 D MANAGEMENT: CMD 'status 2'
19700101 01:04:12 MANAGEMENT: Client disconnected
19700101 01:04:12 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19700101 01:04:12 D MANAGEMENT: CMD 'log 500'
19700101 01:00:00

ca /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 udp cipher aes-256-cbc auth sha1 remote 199.241.146.178 443 comp-lzo yes tun-mtu 1500 mtu-disc yes ns-cert-type server fast-io tun-ipv6 tls-auth /tmp/openvpncl/ta.key 1"

 

 

The message on top is:  "Client: RECONNECTING tls-error"

 

I was using the initial DD-WRT for my router, but just tried upgrading to the latest version by KONG and the issue remains.

 

Any idea why?  Literally nothing (that I know of) changed on my end.

Share this post


Link to post

OMG I've been going crazy trying to resolve the same issue for the last 24 hours!!!! I've installed a pihole server on a vm and thought it had to do with that, but even when I took it out of the loop, I was still getting the RECONNECTING tls-error. 

Removing the Server IP/Name address worked for me too. I NEVER would have thought to take it out on my own, so THANK YOU for posting your resolution!!!

I wonder what has caused this bug to suddenly cause a problem.... Our setup has been working fine with the same settings for a couple of years.

 

Share this post


Link to post

Hello!

Cause of the issue is trivial: in 1970 our certificates are not valid.

19700101 01:04:09 N VERIFY ERROR: depth=1 error=certificate is not yet valid: C=IT ST=IT L=Perugia O=airvpn.org CN=airvpn.org CA emailAddress=info@airvpn.org

So no bug but correct behavior.

According to your own descriptions, it is plausible that the router could not reach the configured NTP server to set the correct date and time.

Kind regards
 

Share this post


Link to post
Guest
This topic is now closed to further replies.
Sign in to follow this  

×
×
  • Create New...