sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli –configure
sudo /Applications/VMware\ Fusion.app/Contents/Library/services/services.sh –stop
sudo /Applications/VMware\ Fusion.app/Contents/Library/services/services.sh –start
The key to customizing Fusion’s networking is the directory /Library/Preferences/VMware Fusion.
sudo nano /Library/Preferences/VMware\ Fusion/networking
There is a file called networking, which is the master configuration file for Fusion networking. You can edit this file with sudo shown above when Fusion is shut down (which also tears down any virtual networks); changes will be picked up and applied the next time you start Fusion.
You can use the following shutdown command: shutdown -r now
A brand-new networking file looks similar to this:
answer VNET_1_DHCP yes
answer VNET_1_DHCP_CFG_HASH F5FEE30FD06F6A58C7B1B1C2497C54BE04676E98
answer VNET_1_HOSTONLY_NETMASK 255.255.255.0
answer VNET_1_HOSTONLY_SUBNET 192.168.32.0
answer VNET_1_VIRTUAL_ADAPTER yes
answer VNET_8_DHCP yes
answer VNET_8_DHCP_CFG_HASH 0AEB0A5DAC06201088354E25F52B115FF3F6609F
answer VNET_8_HOSTONLY_NETMASK 255.255.255.0
answer VNET_8_HOSTONLY_SUBNET 172.16.110.0
answer VNET_8_NAT yes
answer VNET_8_VIRTUAL_ADAPTER yes
In this file, the VNET_1 answers correspond to vmnet1, the included host-only network, and VNET_8 is for vmnet8, the NAT network that all virtual machines that need Internet access use.
I recommend you don’t change either one of these networks’ configurations. Instead, you can add your own networks, supplying new answer directives by adding lines for VNET_2, VNET_3, and so on.
In my example, I needed a new host-only network where I could attach my virtual machines. This network would not have DHCP, and I would want my Mac to have a fixed address on that network. I added these lines to networking, which—once the virtual machines were configured appropriately—allowed my Mac to talk to the other virtual machines (on 10.0.0.1 and 10.0.0.253, in the 10/16 subnet):
answer VNET_2_HOSTONLY_NETMASK 255.255.0.0
answer VNET_2_HOSTONLY_SUBNET 10.0.0.0
answer VNET_2_VIRTUAL_ADAPTER yes
answer VNET_2_VIRTUAL_ADAPTER_ADDR 10.0.0.128