Rafael Weingärtner created CLOUDSTACK-10346:
-----------------------------------------------
Summary: Problem with NAT configuration and VMs not accessing each
other via public IPs
Key: CLOUDSTACK-10346
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10346
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Rafael Weingärtner
Assignee: Rafael Weingärtner
When users create a VPC, and configure a NAT from a public IP to application in
a VM. This VM(applications) are not accessible via public IP for other VMs in
the same VPC.
The problem is in the NAT table. If you take a closer look at rules, you will
see something like:
{code:java}
-A PREROUTING -d publicIP/32 -i eth1 -p tcp -m tcp --dport 80 -j DNAT
--to-destination internalIp:80
{code}
The problem is that according to this rule only packets coming via eth1(public
interface), will be “redirected” to the internal IP. We need an extra entry to
each one of the NAT configurations. For the presented rule, we would need
something like:
{code:java}
-A PREROUTING -d publicIP/32 -i eth2 -p tcp -m tcp --dport 80 -j DNAT
--to-destination internalIp:80
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
