Access localhost without WiFi

[sjordi]

Hi,

I have my Macbook and a Windows 8 Windows VM in Fusion 6.

Now my problem is that for development purposes, I need to access a server on my Mac side from within Windows 8.

Localhost, 127.0.0.1 don't work.

How can I do this knowing that I need it to work WITHOUT wifi. Most of the time I'm in a plane or train and don't have a network.

While at home, no problem, I hit 192.168.1.nn where nn is the fixed address for my Mac, but when I don't have any kind of Ethernet/Wifi connection, then what?

Is there a way to set a fixed IP that Windows will see to talk to the Mac side?
My Fusion is using NAT for its own network needs.

Should I do something else? Bridging? What about my DHCP server at home when connected?
What I want to avoid is to have to change the config each time I'm connected or offline. I need a config that is working once and for all.

Thanks for any (detailed) instructions.

Steve

[WoodyZ · Accepted solution]

localhost is just that! local to the host meaning the system itself, physical or virtual, and therefore one may not access something beyond it!

If you're using NAT then you should be able to access the resource of the Host (OS X) from the Guest OS (VM) via the Host's vmnet8 IP Address whether or not the Host is connected to a physical LAN.

While VMware Fusion is open, then in a Terminal use ifconfig vmnet8 to ascertain its IP Address as shown in the image below.

(Click image to enlarge.)

[sjordi]

Well,

that did it. Even though my server on the Mac side was listing those addresses, I didn't actually see the point.

The one I use now is 192.168.2.1 and it works whether I'm fully offline, over Wifi, over Ethernet. Way cool.

You made my day!

Thanks a lot

Steve

[RodolfoFlores]

Hello

In my case I have the IP address 192.168.0.1 as my gateway. All IP addresses can be changed using the ip command.

Also is possible using the command ifup to assign a virtual network interface, for example with the interface eth0, you can configure eth0:0, eth0:1, etc. as virtual interfaces, to be used with different IP addresses, including local.

Regards

[scott28tt]

You do realise this is a thread from 2013?

It might be better to start your own thread, giving full details of your host OS, guest OS, version of Fusion, and your network adapters.