Uploaded image for project: 'CloudStack'
  1. CloudStack
  2. CLOUDSTACK-10346

Problem with NAT configuration and VMs not accessing each other via public IPs

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • None
    • None
    • None
    • Security Level: Public (Anyone can view this level - this is the default.)
    • None

    Description

      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:

      -A PREROUTING -d publicIP/32 -i eth1 -p tcp -m tcp --dport 80 -j DNAT --to-destination internalIp:80
      

      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:

      -A PREROUTING -d publicIP/32 -i eth2 -p tcp -m tcp --dport 80 -j DNAT --to-destination internalIp:80
      

      Attachments

        Issue Links

          Activity

            People

              rafaelweingartner Rafael Weingärtner
              rafaelweingartner Rafael Weingärtner
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: