Quantcast
Channel: VMware Communities: Message List - VMware vCloud Director
Viewing all articles
Browse latest Browse all 7719

Re: fenced networking static routing

$
0
0

So you are in a double NAT scenario.

 

NAT at the vApp level, and a routed network means a NAT at the Organization level.

 

The fenced vApp will not inherit rules because the external IP for the VM itself will change, and the edge device will be different (IP and rule set).

 

Automatic NAT can happen at the vApp level, but the org will always be a manual task (or automated via the api).

 

 

Since you have a routed network at the Org Network Level, this means you have a single external IP and no way of routing without some sort of rule.  this could be Port Forward or NAT, but you still have to configure a method from getting in from the outside (if that matters).

 

You won't need the port forward or NAT if you only intend to go from the inside (vApp VM) to the outside (public network).  You will need at least a general rule to allow the org network traffic outbound (ANY:1 SNAT)


Viewing all articles
Browse latest Browse all 7719

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>