DD-WRT and Adhara OpenVPN setup

[Thebrynn 1]

Dear all, I am trying to get the new DE server Adhara to work with my DD-WRT router.

 

Every other server works fine (as well as the DE server group IP), but for some reason I can't seem to connect to this 185.104.184.42 IP address.

 

Is there something special to the new servers that we need to set up differently?

 

I use the default UDP 443 port, have AES-256 CBC as the encryption cypher, have the Hash algorithm as SHA1 and have the TLS Cypher as TLS-DHE-RSA-WITH-AES-256-GCM-SHA384

This seems to work for everything but this one server.

 

I have tried changing some of the settings, but without any success at the moment.

 

Does anyone have any ideas?

 

thanks in advance!

 

reason for changing was that Menkib was given me some website browsing issues (some websites can't be resolved, but it does work with other servers).

[Thebrynn 1]

I tried it now again and below you can find the log.

 

it never sends the TLS packet to initiate the connection apparently.

 

When I try to ping / pathping / trace the route to this server I can't seem to reach it.

The other servers in Germany I can reach fine. so not sure what is going on here to be honest.

 

 

Clientlog: 
20170509 21:36:53 I OpenVPN 2.3.12 arm-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [MH] [IPv6] built on Sep 9 2016 
20170509 21:36:53 I library versions: OpenSSL 1.0.2h 3 May 2016 LZO 2.09 
20170509 21:36:53 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:16 
20170509 21:36:53 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts 
20170509 21:36:53 W WARNING: file '/tmp/openvpncl/client.key' is group or others accessible 
20170509 21:36:53 W WARNING: file '/tmp/openvpncl/ta.key' is group or others accessible 
20170509 21:36:53 I Control Channel Authentication: using '/tmp/openvpncl/ta.key' as a OpenVPN static key file 
20170509 21:36:53 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication 
20170509 21:36:53 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication 
20170509 21:36:53 Socket Buffers: R=[180224->180224] S=[180224->180224] 
20170509 21:36:53 I UDPv4 link local: [undef] 
20170509 21:36:53 I UDPv4 link remote: [AF_INET]182.104.184.42:443 
20170509 21:37:36 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16 
20170509 21:37:36 D MANAGEMENT: CMD 'state' 
20170509 21:37:36 MANAGEMENT: Client disconnected 
20170509 21:37:36 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16 
20170509 21:37:36 D MANAGEMENT: CMD 'state' 
20170509 21:37:36 MANAGEMENT: Client disconnected 
20170509 21:37:36 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16 
20170509 21:37:36 D MANAGEMENT: CMD 'state' 
20170509 21:37:36 MANAGEMENT: Client disconnected 
20170509 21:37:36 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16 
20170509 21:37:36 D MANAGEMENT: CMD 'status 2' 
20170509 21:37:36 MANAGEMENT: Client disconnected 
20170509 21:37:36 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16 
20170509 21:37:36 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 182.104.184.42 443 comp-lzo yes tls-client tun-mtu 1500 mtu-disc yes ns-cert-type server fast-io tun-ipv6 tls-auth /tmp/openvpncl/ta.key 1 tls-cipher TLS-DHE-RSA-WITH-AES-256-GCM-SHA384

[go558a83nk 364]

Looks like your ISP is blocking your access to that server.

[Thebrynn 1]

Looks like your ISP is blocking your access to that server.

 

That would be interesting that Deutsche Telekom blocks that server in particular. It's the last one that was installed in Germany to my understanding.

 

Luckily they don't block all the DE AirVPN servers yet :-)

 

I guess smarter to leave it at that, and not reach out to them to ask why I can't reach this IP.

[go558a83nk 364]

 

Looks like your ISP is blocking your access to that server.

 

That would be interesting that Deutsche Telekom blocks that server in particular. It's the last one that was installed in Germany to my understanding.

 

Luckily they don't block all the DE AirVPN servers yet :-)

 

I guess smarter to leave it at that, and not reach out to them to ask why I can't reach this IP.

 

If you can reach other servers using the same protocol and port then it seems they're blocking that IP address.  It may stem from that IP address' previous history - before it belonged to AirVPN.

[Doesi 3]

You have the wrong ip in your setup: 182.104.184.42 <> 185.104.184.42

[Thebrynn 1]

You have the wrong ip in your setup: 182.104.184.42 <> 185.104.184.42

 

Thanks! Well spotted for the original post (edited this one now), but as you can see in my config log I was using the correct IP.

[Doesi 3]

No, you did use the wrong IP. 185.104.184.42 is the correct one and works.

[Thebrynn 1]

No, you did use the wrong IP. 185.104.184.42 is the correct one and works.

 

 

OMG, I am so sorry about that; What a silly copy paste error :/

 

Good news it is indeed working. Not sure where my brain was during these tests.

 

Thanks again for spotting this silly error of mine!

[OpenSourcerer 1442]

It's amazing how fast people come to the conclusion that an ISP is blocking IPs when they run into an issue...

 

If something ever does not work and you suspect your ISP, drop me a note. I'm with Deutsche Telekom, too.