Is there an easy way to make a local client on a local machine talking to a local server think that it is talking to a server on the internet?

Question

I have a local (HTTP) server running on my (Linux) machine (listening on 127.0.0.1:port) and a local application that connects to it as a client. Both the server and client applications are proprietary and I can only change some basic config for both. I have had this set up working fine until recently when the client application was updated. The client application now seems to require that the server it connects to must be "on the internet" so it is disallowing connections to 127.0.0.1 and other "local-like" addresses such as 10.0.*.* and 192.168.*.*.

As a workaround, I am now using ngrok to get a remote address for my local server and the client application happily works with that. However, that is a manual/slow process to run ngrok and update the client application's config and it requires an internet connection and going through ngrok's servers.

I am wondering if there is a way to "fake" an "internet-like" IP address to resolve directly to my local machine.

I have looked into "dynamic DNS" solutions but they require changes to router config that I often don't have control over.

What I am thinking is along the lines of setting some porn site's "internet-like" IP to "resolve" to my local machine on my local machine using some kind of "virtual network adapter" BUT I don't want to spend a lot of time building such a set up. Hence, the question, is there an EASY way to do this?

Answer 1

use iptables?

iptables -t nat  -I OUTPUT --src 0/0 --dst dest_ip -p tcp --dport 80 -j REDIRECT --to-ports 80

(not sure about the chain though) This should in effect redirects --transparently-- any traffic going to dest_ip:80 to localhost:80.

the des_ip is any ip that makes the application happy.

Answer 2

You can add as an alias a "real" IP on the server, i.e. 1.2.3.4/32 and try connecting to this address form the client application, if it's on the same computer. If your client application in on a different computer, use something like 1.2.3.4/24 for the server and 1.2.3.5/24 for the client, provided they're both in the same LAN. This type of addresses is not assigned in the internet, so you won't face any connectivity problems.

Answer 3

You could try an ip address in one of the less well-known reserved, or not routable, ranges, betting on a poor implementation in your client-server application.

Refer to https://en.m.wikipedia.org/wiki/Reserved_IP_addresses

Answer 4

I would use virtualization. You can make a fake little world for your software to live in. This can be as elaborate or as simple as you want. The benefit here is that you can use public IP addresses without messing up networking for the entire LAN you are attached to. Just make sure that the virtual interfaces are set to "host only" or "virtual network only".

You could even make two machines. One client and one server both in the public subnet, so they can talk to each other without routing. This could exist completely in the virtual network and not even be visible to the host, if you desired.

Answer 5

Maybe you can use an Internet simulator like INetSim. It simulates (provides fake) common internet services, so the program thinks it's on the Internet. It is e.g. used for analyzing the network behaviour of malware in a closed and safe environment, and this program is then used to trick it to believe it is the Internet, while it's actually not.

It seems like the same scenario as your, so take a look at it and see if you can use it!