I do all my development on VMWares, as they are cheap and easy to setup and mimic the real deployment environment. I've always used NAT networking on my vmwares rather than put them on the network as standalone bridged items, however, recently I was asked to "share" my latest code on the network. My host hacks didn't get translated so I needed to to forward the port 80 traffic from the Mac to the VM

Turns out its easy - nat.conf is the key. Just add the configuration to

/Library/Application\ Support/VMware\ Fusion/vmnet8/nat.conf

in the incomingtcp configuration.

[incomingtcp]
80 = IP_OF_THE_VMWARE:80

And restart the vmware networking:

sudo /Library/Application\ Support/VMware\ Fusion/boot.sh --restart

I upgraded my vmware fusion and found that all my NAT networking connections stopped working.After much googling and poking around I couldnt find any answers. I found my Bridge networking was working fine, so how to fix NAT? Well after kicking the vmware networking on MAC with:

sudo /Library/Application\ Support/VMware\ Fusion/boot.sh --restart

I saw lots of permission errors and repair messages on the first run. Once I ran it again I still got the following error in the traceback:

Permissions differ on "Library/Application Support/VMware Fusion/VMDKMounter.app/Contents/MacOS/vmware-vmdkMounter", should be -rwxr-xr-x , they are -rwsr-xr-x .
Warning: SUID file 'Library/Application Support/VMware Fusion/VMDKMounter.app/Contents/MacOS/vmware-vmdkMounter' has been modified and will not be repaired.

So to fix I simply changed the permissions to be as they should be!

sudo chmod 755 "/Library/Application Support/VMware Fusion/VMDKMounter.app/Contents/MacOS/vmware-vmdkMounter"
sudo /Library/Application\ Support/VMware\ Fusion/boot.sh --restart

That came up with no errors, so I just restarted networking on my vmwares and volia! All fixed!On my ubuntu vm's I had to remove my networking rules and restart - like so:

sudo rm /etc/udev/rules.d/70-persistent-net.rules
sudo reboot