You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Jayapal Reddy (JIRA)" <ji...@apache.org> on 2017/01/25 11:14:26 UTC

[jira] [Created] (CLOUDSTACK-9757) VPC traffic from vm to additional public subnet is not working

Jayapal Reddy created CLOUDSTACK-9757:
-----------------------------------------

             Summary: VPC traffic from vm to additional public subnet is not working
                 Key: CLOUDSTACK-9757
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9757
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Network Devices
            Reporter: Jayapal Reddy
            Assignee: Jayapal Reddy
             Fix For: 4.10.0.0


1. Add additional Public IP to Physical Network (specify a VLAN ID to isolate traffic),
2. Create PortForward rule in VPC
i) Acquire New IP , which used additional Public IP
ii) Map a VM instance to use this Public IP
3. Observe that when VM ping additional public subnet then it is  not working


For additional public subnet ip SNAT rules are not configured when PF/Staticnat is configured. Due to this PF/StaticNAT VM traffic from to additional public subnet is not SNATed to public ip.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)