[
https://issues.apache.org/jira/browse/CLOUDSTACK-10346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16639093#comment-16639093
]
ASF GitHub Bot commented on CLOUDSTACK-10346:
---------------------------------------------
rhtyd edited a comment 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-427210903
@izenk The basic tests of ingress/egress to/from user VMs to other user VMs
using public SNAT (attached) IP pass for me both when VMs were in (a) different
tiers in the same VPC, (b) across VPCs, (c) in the same tier. Packet marking in
4.11.2.0 is slightly changed to fix a bug where marking a packet with 0x0
failed in the new VR. Routing etc LGTM, I tested the latest 4.11 branch
(4.11.2.0 rc2 + two new commits not related to VR).
----------------------------------------------------------------
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)
