great job, thanks mustaccio. To raise the dead ...
VMware Player 5
outline:
- VNET_# = 0 to 9 (VMnet# i.e. for VMnet1: VNET_1)
- HASH is a 40 digit hex number
File -- Start
File Header:
VERSION=1,0
bridge mode -- other than standard (see addition below)
answer VNET_#_DHCP no
answer VNET_#_VIRTUAL_ADAPTER no
Host-only with DHCP
answer VNET_#_DHCP yes
answer VNET_#_DHCP_CFG_HASH [enter_hash]
answer VNET_#_HOSTONLY_NETMASK 255.255.255.0
answer VNET_#_HOSTONLY_SUBNET 192.168.0.0
answer VNET_#_VIRTUAL_ADAPTER yes
Host-only without DHCP
answer VNET_#_DHCP yes
answer VNET_#_DHCP_CFG_HASH [enter_hash]
answer VNET_#_HOSTONLY_NETMASK 255.255.255.248
answer VNET_#_HOSTONLY_SUBNET 173.239.151.176
answer VNET_#_NAT no
answer VNET_#_VIRTUAL_ADAPTER yes
NAT
answer VNET_#_DHCP yes
answer VNET_#_DHCP_CFG_HASH [enter_hash]
answer VNET_#_HOSTONLY_NETMASK 255.255.255.0
answer VNET_#_HOSTONLY_SUBNET 192.168.1.0
answer VNET_#_NAT yes
answer VNET_#_VIRTUAL_ADAPTER yes
Non-standard bridge mode (i.e. not Auto) Number at the end is VMnet#
answer VNL_DEFAULT_BRIDGE_VNET -1
add_bridge_mapping eth0 0
add_bridge_mapping eth1 1
File --- End
I found that when I run service vmware start
some processes failed. Also, associated & required files were not added or updated, as I had hoped.
FIX: Uninstall VMware Player and then reinstall. Vmware player will use your /etc/vmware/networking file to create a new network setup
To unistall:
vmware-installer -u vmware-player *version.build*
(version.build = Product Version i.e. 5.0.4.1945795; see vmware-installer -l
or the bundle file name for your info)
Note: Standard auto bridge mode does not have an entry, VMnet0, when in bridge (either auto or assigned), is presumed and not included in the file declaration