2 Posts

October 5th, 2015 14:00

Playing around and it seems that the adapter with NAT must be set to Bridged and the most important, don't upgrade the VM to version 8 of VMWare Fusion. It looks like it don't boot completely with this upgrade. So it looks like it's solved :-)

76 Posts

October 7th, 2015 23:00

You can use bridged, NAT, or host-only, but it's just a matter of making sure you are aware of the networking considerations for each networking type.

VMware's KB spells out the networking types used in Fusion here:

http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1022264

Bridged is usually  the easiest as it just allows you to add an IP address to your VM and get it online quickly.  If you don't know the right IP to use on the VM, you can also go with NAT (vmnet8) and just use an IP address in the network assigned to vmnet8.  (As seen from ifconfig on the Mac.)  Mine is set up with 172.16.222.0/24 and the VM's gateway would be 172.16.222.1 I believe.

If you don't want the VM to have external connectivity, host-only (vmnet1) will function just fine. vmnet1 also works well for backend node-to-node communication when running multiple VMs on your Fusion host.  My Macs are using 172.16.73.0/24 on vmnet8.

No Events found!

Top