cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9757) VPC traffic from vm to additional public subnet is not working
Date Wed, 22 Feb 2017 10:50:44 GMT

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

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

Github user jayapalu commented on a diff in the pull request:

    https://github.com/apache/cloudstack/pull/1922#discussion_r102432766
  
    --- Diff: server/src/com/cloud/network/router/CommandSetupHelper.java ---
    @@ -703,6 +722,10 @@ public void createVpcAssociatePublicIPCommands(final VirtualRouter
router, final
                         sourceNatIpAdd = new Pair<IpAddressTO, Long>(ip, ipAddr.getNetworkId());
                         addSourceNat = add;
                     }
    +
    +                if (!firstIP || add) {
    +                    firstIP = false;
    +                }
    --- End diff --
    
    for additional public subnet on delete it is not sure which ip is set to first ip. So
on delete we want to set sourcenat to true for all ips to delete source nat rules. 
    
    @ramkatru 
    I will add above comment.


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

Mime
View raw message