[
https://issues.apache.org/jira/browse/CLOUDSTACK-10346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442867#comment-16442867
]
ASF GitHub Bot commented on CLOUDSTACK-10346:
---------------------------------------------
rafaelweingartner commented on issue #2514: [CLOUDSTACK-10346] Problem with NAT
configuration and VMs not accessing each other via public IPs
URL: https://github.com/apache/cloudstack/pull/2514#issuecomment-382459118
What do you mean by "SNAT"? Are you referring to "enable static NAT" feature
in ACS? This PR is **NOT** addressed to this feature(SNAT). If I enable static
NAT, then everything is fine here. What I am addressing here is the NAT for a
public IP that I allocate for a VPC.
That is probably why my rules are different:
```
root@r-1186-VM:~# iptables-save | grep MARK
-A PREROUTING -i eth2 -m state --state RELATED,ESTABLISHED -j CONNMARK
--restore-mark --nfmask 0xffffffff --ctmask 0xffffffff
-A PREROUTING -i eth1 -m state --state NEW -j CONNMARK --set-xmark
0x1/0xffffffff
```
Then, I executed the command as you suggested.
```
iptables -t mangle -D PREROUTING -i eth1 -m state --state NEW -j CONNMARK
--set-xmark 0x1/0xffffffff
```
The result after that command:
```
root@r-1186-VM:~# iptables-save | grep MARK
-A PREROUTING -i eth2 -m state --state RELATED,ESTABLISHED -j CONNMARK
--restore-mark --nfmask 0xffffffff --ctmask 0xffffffff
```
I then tried the SSH, and it did not work.
Of course, to executed the test, I removed
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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
> Priority: Major
>
> 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)
