Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I want to map the IP address 192.168.1.222 to 127.0.0.1 so that if I use 192.168.1.222 in the web browser or ping command I get the response (and that from my 127.0.0.1).

Is this possible via routing tables or do I have to add some sort of virtual network adapter?

I try to deal with this problem on a Windows 7 machine and have no other options than a Windows XP maybe.

I'm stuck right there.

share|improve this question
    
Don't know if that's possible, but it's easy to do with hostnames. Is it just for one computer? –  Canadian Luke Nov 30 '11 at 15:46
    
Okay, two questions here: 1. If you're trying to get to the local system in a web browser, why not just use 127.0.0.1 all the time? 2. If this is for the local system, why deal with cumbersome IPs at all instead of using the reserved hostname localhost? –  Iszi Nov 30 '11 at 17:11
    
@DiogoRocha Please make your edits more substantial than these. A single character or capitalization of a term aren't nearly relevant enough for an edit that push topics to the front page. This and this topic apply to suggested edits, but the principle holds even once you have editing privileges. Thanks. –  Daniel Beck Nov 30 '11 at 21:35
    
@Luke: I can't work with hostnames so the hosts file is not viable here –  Sebastian Dec 1 '11 at 7:39
    
@Iszi: I need it to get a software think, that there is another machine present. –  Sebastian Dec 1 '11 at 7:39

2 Answers 2

This should work in both Windows 7 and XP, from command window:

route ADD 192.168.1.222 MASK 255.255.255.255 127.0.0.1

If you want the new route to be persistent between reboots:

route -p ADD 192.168.1.222 MASK 255.255.255.255 127.0.0.1
share|improve this answer
    
This method doesn't work. I don't get the ping on 192.168.1.222 to return a response. What I did now was to add multiple IPs to the interface (IP Aliasing) but even this doesn't work since the service I try to communicate with seems to listen to 1 IP only. –  Sebastian Dec 1 '11 at 7:38
2  
Now that I think of it, I'm pretty sure this won't work unless 192.168.1.222 is an IP that actually belongs to the local machine, in which case it would be redundant anyway. It will force the computer to send packets destined for 192.168.1.222 to the loopback, but on the receiving end they'll be dropped if that's not the local IP. –  Iszi Dec 1 '11 at 14:09

You would have to assign the IP address 192.168.1.222 to one of your network interfaces. Merely altering the routing table will not have the desired result; traffic would indeed arrive at the localhost, but your computer will then conclude the message has not yet reached its destination. Lacking any further options of passing the message along, it will then be dropped.

Assigning 192.168.1.222 to one of your physical interfaces would be the simplest solution, but if you do not have a spare interface and do not want your changes to affect the rest of the network, you can create another loopback interface, similar to the one at 127.0.0.1.

The procedure has changed somewhat since Windows XP. Open the device manager via the control panel and in the Action menu, click 'Add legacy hardware'. If this option is missing, the wizard can be started via the executable 'hdwwiz.exe'.

Device manager

When asked, select hardware manually from a list rather than installing it automatically. In the following menus, select 'Network Adapter', 'Microsoft' as manufacturer and look for the 'Microsoft Loopback Adapter'. If the device has been installed correctly, a new network adapter will have appeared in the device manager.

Open the Network and Sharing Center via the control panel and click 'Change adapter settings' in the left bar. The following window will appear, including our newly installed adapter.

Network connections

Open its properties. From the Networking tab, select the IPv4 item and click the Properties button. Enter the IP address you wish to assign to the loopback interface. Because it will be the only interface on its network, we enter '255.255.255.255' as the subnet mask.

IP addresses

Voila.

C:\Users\Marcks>ping 192.168.1.122

Pinging 192.168.1.122 with 32 bytes of data:
Reply from 192.168.1.122: bytes=32 time<1ms TTL=128
Reply from 192.168.1.122: bytes=32 time<1ms TTL=128
Reply from 192.168.1.122: bytes=32 time<1ms TTL=128
Reply from 192.168.1.122: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.122:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.