Unable to connect with DD-WRT

[q60b 0]

Hi,

 

I was using the dd-wrt with AirVPN for more than a year. Unfortunately it has stopped working since last couple of days.

I have tried and updated the certificates but of new use.

 

I am posting the log below and the router settings are attached. Can someone please help?

 

Serverlog Clientlog 20180425 19:13:15 I OpenVPN 2.3.0 mipsel-unknown-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on Mar 25 2013
20180425 19:13:15 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:16
20180425 19:13:15 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
20180425 19:13:15 W WARNING: file '/tmp/openvpncl/client.key' is group or others accessible
20180425 19:13:15 W WARNING: file '/tmp/openvpncl/ta.key' is group or others accessible
20180425 19:13:15 I Control Channel Authentication: using '/tmp/openvpncl/ta.key' as a OpenVPN static key file
20180425 19:13:15 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
20180425 19:13:15 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
20180425 19:13:15 Socket Buffers: R=[114688->131072] S=[114688->131072]
20180425 19:13:15 I UDPv4 link local: [undef]
20180425 19:13:15 I UDPv4 link remote: [AF_INET]213.152.161.100:53
20180425 19:13:15 TLS: Initial packet from [AF_INET]213.152.161.100:53 sid=bee09a1d eb5855ac
20180425 19:14:05 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20180425 19:14:05 D MANAGEMENT: CMD 'state'
20180425 19:14:05 MANAGEMENT: Client disconnected
20180425 19:14:05 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20180425 19:14:05 D MANAGEMENT: CMD 'state'
20180425 19:14:05 MANAGEMENT: Client disconnected
20180425 19:14:05 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20180425 19:14:05 D MANAGEMENT: CMD 'state'
20180425 19:14:05 MANAGEMENT: Client disconnected
20180425 19:14:05 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20180425 19:14:05 D MANAGEMENT: CMD 'log 500'

[go558a83nk 362]

If it was working before but not now

 

1) check to make sure the server you're trying to connect to is operational

2) perhaps something changed in your local network or your ISP and UDP 53 (the port and protocol you're trying to use according to the log) is now blocked.  Try TCP 443 just to see if that's the problem.

[q60b 0]

Thanks for your reply.

I have tried all these servers

213.152.161.100
213.152.162.169
213.152.161.169
213.152.161.29
213.152.161.164

 

Also I have tried TCP 443 / UDP 443 / 53  / 80

 

Any other options i have to check.

 

PS:

I am able to connect these servers using windows client software "Eddie" and its working fine.

[Koko199164 0]

Hello,

 

I have been connecting with a DD-WRT router device sha1 since 11/23/2015,  server Merope (the one I use) was down today 05/05/2018 at 4:32 AM for 12m 57s.

​After being disconnected at 4:32 AM, I am also unable to connect with router DD-WRT device sha1 (connection is refused).

 

1. server Merope is now operational.

2. Nothing has changed in my LAN and I already was using TCP 443.

 

I was thinking of creating new certificates for my router but that did not work for q60b.

 

Thank you.

[go558a83nk 362]

Hello,

 

I have been connecting with a DD-WRT router device sha1 since 11/23/2015,  server Merope (the one I use) was down today 05/05/2018 at 4:32 AM for 12m 57s.

​After being disconnected at 4:32 AM, I am also unable to connect with router DD-WRT device sha1 (connection is refused).

 

1. server Merope is now operational.

2. Nothing has changed in my LAN and I already was using TCP 443.

 

I was thinking of creating new certificates for my router but that did not work for q60b.

 

Thank you.

 

 

others are reporting that the LA servers are refusing connections

[Koko199164 0]

Thank you go558a83nk.

 

I tried the Windows client and discovered that any server starting with 199. ( both LA and Dallas servers would not let me connect) refused my connection attempts.

 

I will switch to using the Windows client and other than 199. servers for now and monitor the situation until it is resolved.

 

Again, thank you for your speedy reply.

[go558a83nk 362]

Thank you go558a83nk.

 

I tried the Windows client and discovered that any server starting with 199. ( both LA and Dallas servers would not let me connect) refused my connection attempts.

 

I will switch to using the Windows client and other than 199. servers for now and monitor the situation until it is resolved.

 

Again, thank you for your speedy reply.

 

I was connecting to the Dallas servers this morning just fine.

[Koko199164 0]

I did not try all the Dallas servers but give Chamaeleon a try, it still will not let me connect using the Windows client.

 

I am currently using one of the Fremont servers, Heze.

 

Thank you for your help.