I finally got this to work last night and it was thrilling and disappoint at the same time. The disappointment came from the limitations of fusion.
- open a terminal session and type in the following command -
cat /Library/Preferences/VMware\ Fusion/networking
output will look like this:
answer VNET_1_DHCP yes
answer VNET_1_DHCP_CFG_HASH 92E246053EEA6B7CB0B82DC219EF1718D17C33E9
answer VNET_1_HOSTONLY_NETMASK 255.255.255.0
answer VNET_1_HOSTONLY_SUBNET 172.16.253.0
answer VNET_1_VIRTUAL_ADAPTER yes
answer VNET_3_DHCP no
answer VNET_3_NAT no
answer VNET_3_VIRTUAL_ADAPTER no
answer VNET_8_DHCP yes
answer VNET_8_DHCP_CFG_HASH 62D54CAB586054004EC0B057F4EF4E7704F14749
answer VNET_8_HOSTONLY_NETMASK 255.255.255.0
answer VNET_8_HOSTONLY_SUBNET 192.168.185.0
answer VNET_8_NAT yes
answer VNET_8_VIRTUAL_ADAPTER yes
add_bridge_mapping en0 2
If you look closely and VNET 1 and VNET 8, it gives you the 2 subnets that you can use to set up your VM devices so you can access your device from the external interface. In this case, the subnets are 172.16.253.0/24 and 192.168.185.0/24.
Set your adapters to the following and you should be home free (I configured my external interface on port 1.1 on the LTM)
net adapter 1 = bridged
net adapter 2 = host only
net adapter 3 = host only
net adapter 4 = host only
add a default route for your external interface. ( I used 172.16.253.1 ). I also ran a continuos ping in terminal until I saw the external gate respond and also the external interface on my LTM.