You will need to edit the "/Library/Application Support/VMware Fusion/networking" file and the target Virtual Machine's .vmx configuration file in order to create and use additional VMnets. All editing should be done with the Virtual Machine(s) shutdown, not suspended and VMware Fusion closed.
This is a quick, dirty and incomplete tutorial on the contents of the networking file.
Contents of Normal File:
VERSION=1,0
answer VNET_1_DHCP yes
answer VNET_1_DHCP_CFG_HASH A062EE6F8CFF88B693E9281275179B61C9FE9911
answer VNET_1_HOSTONLY_NETMASK 255.255.255.0
answer VNET_1_HOSTONLY_SUBNET 172.16.241.0
answer VNET_1_VIRTUAL_ADAPTER yes
answer VNET_8_DHCP yes
answer VNET_8_DHCP_CFG_HASH 91B706EF95D821D1F1499BFE3869E06E108E4697
answer VNET_8_HOSTONLY_NETMASK 255.255.255.0
answer VNET_8_HOSTONLY_SUBNET 192.168.70.0
answer VNET_8_NAT yes
answer VNET_8_VIRTUAL_ADAPTER yes
Okay lest break this down into relevant sections and in the next block of code the "answer VNET_(n)_DHCP_CFG_HASH" lines have been removed as these are generated by Fusion and are not User editable and you do not need to add it as it will automatically be added when the Virtual Network is restarted..
This next section of code is for the Default Host Only Network VMnet1:
answer VNET_1_DHCP yes
answer VNET_1_HOSTONLY_NETMASK 255.255.255.0
answer VNET_1_HOSTONLY_SUBNET 172.16.241.0
answer VNET_1_VIRTUAL_ADAPTER yes
This next section of code is for the Default NAT Network VMnet8:
answer VNET_8_DHCP yes
answer VNET_8_HOSTONLY_NETMASK 255.255.255.0
answer VNET_8_HOSTONLY_SUBNET 192.168.70.0
answer VNET_8_NAT yes
answer VNET_8_VIRTUAL_ADAPTER yes
You can add another block using the above blocks as an example however change the VMNET_(n) to the appropriate number 2 - 7 or 9 and leave VNET_1 and VNET_8 alone as some functions require valid default networks or you'll break the virtual network infrastructure.
As an example if another Host Only VMnet is needed then add the following as an example:
answer VNET_2_DHCP yes
answer VNET_2_HOSTONLY_NETMASK 255.255.255.0
answer VNET_2_HOSTONLY_SUBNET 172.16.128.0
answer VNET_2_VIRTUAL_ADAPTER yes
Also as an example if you didn't what the Host to have the vmnet2 virtual network adapter and only the Virtual Machines have access to the VMnet2 you change "yes" to "no" on "answer VNET_2_VIRTUAL_ADAPTER". This would isolate VMnet2 from the Host since saying "no" would remove the vmnet2 virtual network adapter from the Host.
Obviously you can also say "no" to "answer VNET_2_DHCP" if you do not want the DHCP Server for that VMnet. This is useful if one of the Guests is acting as a DHCP Server.
To edit the "/Library/Application Support/VMware Fusion/networking" file do the following in a Terminal (/Applications/Utilities/Terminal):
Hint: Copy and Paste each command one at a time.
cd "/Library/Application Support/VMware Fusion"
sudo ./boot.sh --stop
sudo nano ./networking
sudo ./boot.sh --start
After restarting the virtual network you'll need to edit the target Virtual Machine(s) .vmx configuration file adding the following as an example:
ethernet0.connectionType = "custom"
ethernet0.vnet = "vmnet2"
ethernet0.bsdName = "vmnet2"
ethernet0.displayName = "Custom Host Only VMnet2"
Note: Do not then select "Custom Host Only VMnet2" from the VMware Fusion GUI Virtual Machine Network Settings as it will break the manual edits in the .vmx configuration file and you can ignore the fact that the status light on the "Custom Host Only VMnet2" in the list is grayed out, it still works.
