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 2014/02/06 14:04:10 UTC

[jira] [Resolved] (CLOUDSTACK-6041) [Automation] Creating port forwarding rule for secondary IP (ranges - 172.16.x.x and 192.168.x.x) in Shared Network fails with "Invalid vm ip address"

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-6041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jayapal Reddy resolved CLOUDSTACK-6041.
---------------------------------------

    Resolution: Duplicate

> [Automation] Creating port forwarding rule for secondary IP (ranges - 172.16.x.x and 192.168.x.x) in Shared Network fails with "Invalid vm ip address"
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6041
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6041
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.4.0
>         Environment: Observed on VMware. Not yet verified on Xen and KVM.
>            Reporter: Gaurav Aradhye
>              Labels: automation
>             Fix For: 4.4.0
>
>
> This works for 10.x.x.x
> Steps to reproduce:
> 1) Create a shared network (PF enabled) with range in 172.16.x.x or 192.168.x.x
> 2) Deploy a VM in this and add secondary IP to the default NIC of VM
> 3) Acquire a public IP in the shared network and try to create a NAT rule using this public ip to the secondary IP of VM
> Operation fails.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)