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 19:58:00 GMT

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

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-382510000
 
 
   @rafaelweingartner yes I've updated https://github.com/apache/cloudstack/pull/2579, do
review that. Meanwhile, in your env can you post the following:
   ```
   ip route show table Table_eth1
   ```
   
   Mine looks like this:
   ```
   # ip route show table Table_eth1
   default via 192.168.1.1 dev eth1 proto static 
   throw 10.1.1.0/24 proto static 
   throw 10.1.2.0/24 proto static 
   throw 192.168.1.0/24 proto static
   ```
   
   You can add routing rule like this: (replace cidr with your VPC tiers cidrs, this assumes
that eth1 is public nic for VPC VR which usually is)
   ```
   ip route add throw 10.1.1.0/24 table Table_eth1 proto static
   ip route add throw 10.1.2.0/24 table Table_eth1 proto static
   ```

----------------------------------------------------------------
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