Cannot connect to my HDA over OpenVPN

Post Reply
sleife
Posts: 79
Joined: Tue Nov 02, 2010 2:56 am

Cannot connect to my HDA over OpenVPN

Postby sleife » Fri Jan 11, 2013 6:17 am

Hi everybody

I have to change my Gateway IP for the HDA. From 192.168.1.x to 172.168.0.x
But no my VPN doesn't work anymore.

- I reinstalled the openVPN Client.


I think the problem is that i came with the same IP Range to my home Network but i cant believe this is a problem. Here's the log:
Fri Jan 11 13:02:46 2013 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 11 13:02:47 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Fri Jan 11 13:02:47 2013 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 11 13:02:48 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Fri Jan 11 13:02:48 2013 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 11 13:02:49 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Fri Jan 11 13:02:49 2013 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 11 13:02:50 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Fri Jan 11 13:02:50 2013 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 11 13:02:51 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Fri Jan 11 13:02:51 2013 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 11 13:02:52 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Fri Jan 11 13:02:52 2013 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 11 13:02:53 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Fri Jan 11 13:02:53 2013 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 11 13:02:54 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Fri Jan 11 13:02:54 2013 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 11 13:02:55 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Fri Jan 11 13:02:55 2013 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 11 13:02:56 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Fri Jan 11 13:02:56 2013 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 11 13:02:57 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Fri Jan 11 13:02:57 2013 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 11 13:02:59 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Fri Jan 11 13:02:59 2013 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 11 13:03:00 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Fri Jan 11 13:03:00 2013 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 11 13:03:01 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Fri Jan 11 13:03:01 2013 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 11 13:03:02 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Fri Jan 11 13:03:02 2013 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 11 13:03:04 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Fri Jan 11 13:03:04 2013 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 11 13:03:05 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Fri Jan 11 13:03:05 2013 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 11 13:03:06 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Fri Jan 11 13:03:06 2013 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 11 13:03:07 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Fri Jan 11 13:03:07 2013 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 11 13:03:08 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Fri Jan 11 13:03:08 2013 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 11 13:03:10 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Fri Jan 11 13:03:10 2013 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 11 13:03:11 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Fri Jan 11 13:03:11 2013 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 11 13:03:12 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Fri Jan 11 13:03:12 2013 Route: Waiting for TUN/TAP interface to come up...
Fri Jan 11 13:03:13 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Fri Jan 11 13:03:13 2013 WARNING: potential route subnet conflict between local LAN [192.168.0.0/255.255.255.0] and remote VPN [192.168.0.0/255.255.255.0]
Fri Jan 11 13:03:13 2013 C:\WINDOWS\system32\route.exe ADD 192.168.0.0 MASK 255.255.255.0 10.8.0.5
Fri Jan 11 13:03:13 2013 C:\WINDOWS\system32\route.exe ADD 10.8.0.1 MASK 255.255.255.255 10.8.0.5
SYSTEM ROUTING TABLE
0.0.0.0 0.0.0.0 192.168.0.1 p=0 i=11 t=4 pr=3 a=82 h=0 m=25/0/0/0/0
10.8.0.1 255.255.255.255 10.8.0.5 p=0 i=11 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=18409 h=0 m=306/0/0/0/0
127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=18409 h=0 m=306/0/0/0/0
127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=18409 h=0 m=306/0/0/0/0
169.254.0.0 255.255.0.0 169.254.178.75 p=0 i=23 t=3 pr=3 a=18382 h=0 m=286/0/0/0/0
169.254.178.75 255.255.255.255 169.254.178.75 p=0 i=23 t=3 pr=3 a=18382 h=0 m=286/0/0/0/0
169.254.255.255 255.255.255.255 169.254.178.75 p=0 i=23 t=3 pr=3 a=18382 h=0 m=286/0/0/0/0
192.168.0.0 255.255.255.0 192.168.0.94 p=0 i=11 t=3 pr=3 a=82 h=0 m=281/0/0/0/0
192.168.0.0 255.255.255.0 10.8.0.5 p=0 i=11 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
192.168.0.94 255.255.255.255 192.168.0.94 p=0 i=11 t=3 pr=3 a=82 h=0 m=281/0/0/0/0
192.168.0.255 255.255.255.255 192.168.0.94 p=0 i=11 t=3 pr=3 a=82 h=0 m=281/0/0/0/0
192.168.56.0 255.255.255.0 192.168.56.1 p=0 i=22 t=3 pr=3 a=18388 h=0 m=276/0/0/0/0
192.168.56.1 255.255.255.255 192.168.56.1 p=0 i=22 t=3 pr=3 a=18388 h=0 m=276/0/0/0/0
192.168.56.255 255.255.255.255 192.168.56.1 p=0 i=22 t=3 pr=3 a=18388 h=0 m=276/0/0/0/0
224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=18409 h=0 m=306/0/0/0/0
224.0.0.0 240.0.0.0 192.168.56.1 p=0 i=22 t=3 pr=3 a=18392 h=0 m=276/0/0/0/0
224.0.0.0 240.0.0.0 169.254.178.75 p=0 i=23 t=3 pr=3 a=18392 h=0 m=286/0/0/0/0
224.0.0.0 240.0.0.0 192.168.0.94 p=0 i=11 t=3 pr=3 a=97 h=0 m=281/0/0/0/0
255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=18409 h=0 m=306/0/0/0/0
255.255.255.255 255.255.255.255 192.168.56.1 p=0 i=22 t=3 pr=3 a=18392 h=0 m=276/0/0/0/0
255.255.255.255 255.255.255.255 169.254.178.75 p=0 i=23 t=3 pr=3 a=18392 h=0 m=286/0/0/0/0
255.255.255.255 255.255.255.255 192.168.0.94 p=0 i=11 t=3 pr=3 a=97 h=0 m=281/0/0/0/0
SYSTEM ADAPTER LIST
TAP-Win32 Adapter V9
Index = 23
GUID = {7C94FF2B-41E7-471C-8D7F-3F1CDA57FE44}
IP = 169.254.178.75/255.255.0.0
MAC = 00:ff:7c:94:ff:2b
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV = 0.0.0.0/255.255.255.255
DHCP LEASE OBTAINED = Fri Jan 11 13:03:13 2013
DHCP LEASE EXPIRES = Fri Jan 11 13:03:13 2013
DNS SERV =
Microsoft Virtual WiFi Miniport Adapter
Index = 15
GUID = {D84F524F-BD30-4B39-876E-1FA35B189391}
IP = 0.0.0.0/0.0.0.0
MAC = 00:24:d7:40:ce:8d
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Fri Jan 11 13:03:13 2013
DHCP LEASE EXPIRES = Fri Jan 11 13:03:13 2013
DNS SERV =
Dell Wireless 5540 HSPA Mini-Card Network Adapter
Index = 14
GUID = {9BE2BEFD-C938-4015-9520-32625E2CB2AC}
IP = 0.0.0.0/0.0.0.0
MAC = 02:80:37:ec:02:00
GATEWAY = 0.0.0.0/255.255.255.255
DNS SERV =
Bluetooth-Gerät (PAN)
Index = 13
GUID = {56E3B7CC-13EA-4B5B-8C1C-CFA5F0E0B2C7}
IP = 0.0.0.0/0.0.0.0
MAC = 5c:ac:4c:f9:f8:90
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Fri Jan 11 13:03:13 2013
DHCP LEASE EXPIRES = Fri Jan 11 13:03:13 2013
DNS SERV =
Intel(R) Centrino(R) Ultimate-N 6300 AGN
Index = 11
GUID = {8A7CDE07-ADE6-4668-A1F1-B8031EEE1CB8}
IP = 192.168.0.94/255.255.255.0
MAC = 00:24:d7:40:ce:8c
GATEWAY = 192.168.0.1/255.255.255.255
DHCP SERV = 192.168.0.1/255.255.255.255
DHCP LEASE OBTAINED = Fri Jan 11 13:01:51 2013
DHCP LEASE EXPIRES = Mon Jan 21 13:01:51 2013
DNS SERV = 192.168.0.1/255.255.255.255
VirtualBox Host-Only Ethernet Adapter
Index = 22
GUID = {04C89E29-67C9-498B-A824-20715CA15D57}
IP = 192.168.56.1/255.255.255.0
MAC = 08:00:27:00:18:7f
GATEWAY = 0.0.0.0/255.255.255.255
DNS SERV =
Fri Jan 11 13:03:13 2013 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )
Top
User avatar
bigfoot65
Project Manager
Posts: 11924
Joined: Mon May 25, 2009 4:31 pm

Re: Cannot connect to my HDA over OpenVPN

Postby bigfoot65 » Fri Jan 11, 2013 11:00 am

Did you execute the hda-change-gw script?

http://wiki.amahi.org/index.php/Change_IP_Address

Might require a reboot of the HDA as well.
ßîgƒσστ65
Applications Manager

My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Top
sleife
Posts: 79
Joined: Tue Nov 02, 2010 2:56 am

Re: Cannot connect to my HDA over OpenVPN

Postby sleife » Sun Jan 13, 2013 7:33 am

Yes i did excatly this one to change the ip.

More then one reboot since the last ip change.
Top
User avatar
bigfoot65
Project Manager
Posts: 11924
Joined: Mon May 25, 2009 4:31 pm

Re: Cannot connect to my HDA over OpenVPN

Postby bigfoot65 » Sun Jan 13, 2013 8:10 am

That problem may be exactly what you pointed out. I have heard that using the same IP address range causes things not to work. Maybe try it from a wireless hot spot with a different IP range to see if the issue persists.

Read under troubleshooting.

http://wiki.amahi.org/index.php/OpenVPN
ßîgƒσστ65
Applications Manager

My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Top
sleife
Posts: 79
Joined: Tue Nov 02, 2010 2:56 am

Re: Cannot connect to my HDA over OpenVPN

Postby sleife » Thu Jan 17, 2013 6:07 am

Ok i tried on another lan network with another range. It works..
so now my question, why does the same iprange not works??
Top
User avatar
bigfoot65
Project Manager
Posts: 11924
Joined: Mon May 25, 2009 4:31 pm

Re: Cannot connect to my HDA over OpenVPN

Postby bigfoot65 » Thu Jan 17, 2013 7:46 am

Not sure if that is a shortfall of OpenVPN. Might wanna check the internet.
ßîgƒσστ65
Applications Manager

My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Top
Post Reply

Return to “VPN”

Who is online

Users browsing this forum: No registered users and 8 guests