cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9757) VPC traffic from vm to additional public subnet is not working
Date Thu, 23 Feb 2017 14:36:44 GMT


ASF GitHub Bot commented on CLOUDSTACK-9757:

Github user ustcweizhou commented on the issue:
    LGTM as it is same to commit edd839ab10226760749d4fc15703a41eddc1dfdd
    not tested yet, as VPC with RVR is working fine, so I assume this fixes the issue in VPC
with single VR.

> VPC traffic from vm to additional public subnet is not working
> --------------------------------------------------------------
>                 Key: CLOUDSTACK-9757
>                 URL:
>             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:
> 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

This message was sent by Atlassian JIRA

View raw message