[
https://issues.apache.org/jira/browse/CLOUDSTACK-10346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16443413#comment-16443413
]
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-382577158
@rhtyd sorry the late reply, but the testing took much more time than
expected.
PR #2579 is not working here. System VMs start just fine, but VRs do not.
The VR go to Running state, and then ACs starts to apply configurations in it,
and then the scripts you changed are executed, and VR stops being reachable via
XAPI interface.
I tested with current master, and it is working just fine. However,
differently, from the 4.9.3.0 that we have noticed a problem with NAT, SNAT is
not working (in our 4.9, it was working just fine).The normal NAT is working
(this was not working for our 4.9 here). Go figure!? Can you get master and do
some testing too?
My hosts are XenServer 6.5/7.2. Did you test with XenServer or only with KVM?
PR #2514 was intended to fix the normal NAT, which does not seem to be
broken in master anymore. Therefore, I think we can close it. We need however
to check this errors before releasing a new version. I will re-test again with
master before closing my PR. If something change, I will let you know.
----------------------------------------------------------------
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)
