1

I am one of those angry American users who wants to use a VPN and deprive my ISP of my browsing history. Setting it up was fairly easy and it works fine. However, I found that when I use it, my dynamic DNS domain name seems to not be working. What I mean by this is:

I ssh to myself normally using "mydomain:~$ ssh me@myowndomainname.noip.com" and it works fine.

I turn on the VPN client. I verify that my IP address is now somewhere in Germany.

But then I try the same command and it says cannot connect to host, host is unavailable.

My initial thought was that the Noip update client hadn't run yet, but I could ping myowndomainname.noip.com just fine. I tried waiting 30 mins (the update client is set to check every 30 mins). Still no dice.

I run a VNC version of my desktop at home and need to reverse telecommute frequently...often to check something online like my bank account that I don't want work folks to see.

Can anyone tell me what's causing this? Is it a port-forwarding problem? My VPN allows me to open ports, but I don't know how to set up a proper connection. Do I need to be sshing to the VPN machine's IP address, not my Noip domain?

Also, does anyone know if I'll be getting the SAME IP address each time I use my VPN? If so, it seems relatively simple to make that address the one the Noip uses for the dynamic dns.

Please note: I have seen some similar questions but none with clear answers and/or command line instructions on how to set this up. Usually the answers are just "have you tried this?" For instance, a similar post has an answer of "Most people use a virtual machine" but it doesn't say how to set that up or what the virtual machine will need. Other answers seem to suggest that port-forwarding will solve it, but I don't know how to set that up to a VPN either. I run VNC, but this seems to happen both on VNC and on my local machine. For instance, running the VPN client either in a VNC window OR locally changes the IP address for both. So why would this solve my problem?

Vomit IT - Chunky Mess Style
  • 42,624
confused
  • 191

1 Answers1

1

When you use A VPN Service, all the traffic is routed from your Computer to the VPN Server and then to the internet.

When you try to connect to your SSH from your ISP's ip address, your computer gets the request but its replies through the VPN, so a proper connection cannot be achieved since a different machine answering to the request. Handshake cannot be done.

The problem you're describing is called Asynchronous Routing.

You should make modifications to the route tables in order your computer route the ssh connection through your landline and the rest of the traffic through the VPN.

If you want however to access your SSH through your VPN, like you mentioned you have to portforward through your VPN and run the NOIP Update script when you get a VPN IP from the Service you are using.

The question you made about if you will always get the same VPN IP, is strictly depends on the VPN Provider you use.

You can research a bit more on this thread on ArchLinux forums where a user had the same issue with you.

Devian
  • 596