[
https://issues.apache.org/jira/browse/CLOUDSTACK-9757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15886889#comment-15886889
]
ASF subversion and git services commented on CLOUDSTACK-9757:
-------------------------------------------------------------
Commit 48cbef6d248551a446e1e6a293001037e9cbb9a2 in cloudstack's branch
refs/heads/master from [~rajanik]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=48cbef6 ]
Merge pull request #1922 from Accelerite/vpcApub
CLOUDSTACK-9757: Fixed issue in traffic from additional public subnetAcquire ip
from additional public subnet and configure nat on that ip.
After this pick any from that network and access additional public subnet from
this vm. Traffic is supposed to go via additional public subnet interface in
the VR.
* pr/1922:
CLOUDSTACK-9757: Fixed issue in traffic from additional public subnet
Signed-off-by: Rajani Karuturi <rajani.karut...@accelerite.com>
> 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.15#6346)
