cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-10346) Problem with NAT configuration and VMs not accessing each other via public IPs
Date Wed, 18 Apr 2018 15:37:00 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-10346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442704#comment-16442704
] 

ASF GitHub Bot commented on CLOUDSTACK-10346:
---------------------------------------------

rhtyd 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-382410765
 
 
   @rafaelweingartner I've reproduce the issue, will send a fix in separate PR. @ustcweizhou
is right, we can solve this using routing tables. As far as iptables nat rules are concerned,
the sequence and something redudant rules can be mess. Also between VPC and normal isolated
network VRs, the private and public network interfaces changes.
   
   Update: it's weird, I found that the issue is caused by mangle rules on packets. I'll fixed
the add route method as well. Can anyone advise why we mark packets?

----------------------------------------------------------------
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:
users@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)

Mime
View raw message