How to fake ip at localhost without LoopBack

Question

How can i fake an ip on my own PC? for example if there were an ip address lets say 201.91.81.71, that Host is somewhere outside of my red and is hosting a webserver. How can set a website on my own PC, and when i go to browser and try to explore 201.91.81.71 it actually explore the website at my own PC? pd: I need it with IP addresses not domain names, since I need to implement it on a non-web service.

First guess was installing a LoopBack with 201.191.81.71 as ip, but since some times the subnet works and some other it doesn't isn't a stable solution. Second guess was adding a route to route table :

route add 201.91.81.71 mask 255.255.255.255 192.168.1.2

192.168.1.2 is the ip address of my NIC.

If i could add this route it would work but windows doesn't let me do so.

route add 201.91.81.71 mask 255.255.255.255 127.0.0.1

it doesn't let me set as gateway 127.0.0.1 if 201.91.81.71 isn't set in a NIC, so thats why i set sometimes loopback and this route add is auto, but it needs a subnet mask which doesn't match the ip and cannot set 255.255.255.255, im in real throubles here. can i get some help? thx.

Solution 1

It might work if you add a second IP address on your physical nic. Nothing could be routed to it from outside of your network, because its network address would not match the network address of your gateway, but you would still be able to address it from your computer, and any other computer on the subnet that has the same network address.

I think that would allow you to create an endpoint for that IP address without impacting any other listeners already on your regular IP address. Of course you would need to make sure that your production endpoints were not set up to attach to all of your IP addresses, if there was a conflict.

For example if you have a web server on the Internet with an address of 74.1.1.58/28, with the web service bound to 74.1.1.50:80, you can add addresses that are not in the 74.1.1.50/28 subnet without impacting other devices there. So if you added 201.91.81.71/24 you could bind a new web service to 201.91.81.71:80 and direct traffic there.

The route table would be automatically configured then to see the subnet 201.91.81.0/24 as a local subnet, so if your browser took you there, that is what you would see. Nothing else on the subnet would be available, so you might want to make it smaller by using a larger bit mask. I'm not sure if a 32 bit mask is allowed on the interface however.

Solution 2

Use the Microsoft Loopback network driver to create a fake network interface on your machine and assign it your IP address.

I got this from the answer to this Stack Overflow question.

Comments

[LawrenceC]

The metric on your second loopback adapter with 201.191.81.71 needs to be higher than the metric on your actual Internet-facing network adapter. That should make Windows prefer the loopback over the Internet-facing adapter. The "ROUTE CHANGE" command will do this. Also make sure you're doing an "arp -d" after changing things like this to reset your ARP table.

[sexer]

ill try this one

[sexer]

yeah, but it woks somethimes...

[sexer]

yeah, this is the solution im using at the moment but in after an alternative way...

[sexer]

============================================================‌​===== Another failure :( nope it didn't work, The effect I wanna get would get me a ping to 127.0.0.1 when i pinged to 201.91.81.71, and Im not getting it with this... thx though :(

[sexer]

this is on my original post, im looking for something else.

[Simon]

@sexer so why did u accept this answer :-)

[sexer]

is the first time i ever ask in this site. didn't know bout terms like accepted answer. I just clicked the check. anyway this was the closer and never tried-yet way to get a solution.