Playing with this problem for some time now and I just can't get it working. I'm probably missing something very obvious.
I have created two VMs inside a vApp which is directly connected to the organisational network, which is connected to my internal home network over a vShield Edge. See picture.
The vCloud VMs are running on two ESXi hosts. On the host I have created the dvSwitch dvPG-External-Cloud with VLAN ID 0. The rest of my homenetwork is also running on VLAN 0. After I created an organisational network, the dvs.vcdvsorgnet-prod-192-168-10 dvPortGroup was created by vCloud, connected to VLAN 150 (also available on the physical switches).
When I now attach a vApp to the Org network and create two VMs in this vApp which are connected directly to the org network, the VMs can ping eachother also when on different hosts. They cannot ping the Edge device ( 192.168.10.254 ) or make any other connection to the outside world.
Why??? What am I missing?
Is a SNAT / DNAT rule required? I did enable a SNAT rule with original IP 192.168.10.0/24 for any port to 192.168.0.161 any port any protocol. Does the Edge appliance have to be redeployed after the change?
Any help is much appreciated....
SNAT is required from my understanding. Are you applying the rule on the external interface?
Hope that helps. I'm currently knee deep on an issue I'm trying to resolve where some of the hosts have connectivity and some don't through the vShield.
Well, the SNAT rule I created was wrong so I corrected it to be a NAT rule on the external interface. But the biggest mistake was that I hadn't created a sub-allocated IP address to be used in the NAT rule.
I've written a blog post on it: VMware vCloud networking for Dummies.