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

ASF GitHub Bot commented on CLOUDSTACK-9757:
--------------------------------------------

GitHub user jayapalu reopened a pull request:

    https://github.com/apache/cloudstack/pull/1922

    CLOUDSTACK-9757: Fixed issue in traffic from additional public subnet

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


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Accelerite/cloudstack vpcApub

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1922.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1922
    
----
commit 0645cbe14c33c8271bd2f13785288c0be0c8038c
Author: Jayapal <jayapal.ur...@accelerite.com>
Date:   2017-02-22T10:50:48Z

    CLOUDSTACK-9757: Fixed issue in traffic from additional public subnet

----


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

Reply via email to