[ https://issues.apache.org/jira/browse/CLOUDSTACK-10346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16443060#comment-16443060 ]
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-382498868 The first time when I saw this `throw` clause in the @ustcweizhou comments, I googled and I found this: > throw - a special control route used together with policy rules. If such a route is selected, lookup in this table is terminated pretending that no route was found. Without policy routing it is equivalent to the absence of the route in the routing table. The packets are dropped and the ICMP message net unreachable is generated. The local senders get an ENETUNREACH error. That is why I said I do not understand who that `throw` option can solve the NAT translation that we are having ---------------------------------------------------------------- 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)