[
https://issues.apache.org/jira/browse/CLOUDSTACK-9165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059582#comment-15059582
]
ASF GitHub Bot commented on CLOUDSTACK-9165:
--------------------------------------------
GitHub user SudharmaJain opened a pull request:
https://github.com/apache/cloudstack/pull/1246
CLOUDSTACK-9165 unable to use reserved IP range in a network for exte…
…rnal VMs
Repro Steps
------------------
1. Create an isolated network with CIDR 192.168.200.0/24.
2. Edit the CIDR to 192.168.200.0/25.
3. Perform Network restart with cleanup.
4. Network Restart with Cleanup, it was successful.
4. Add external VM to the network with IP 192.168.200.150/24 to the
network.
5. After restart Netmask1 displayed CIDR 192.168.200.150/25 and Network
CIDR as 192.168.200.150/24.
6. Create an instance from cloudstack.
7. Ping the VM from external VM.
Before Applying the fix
-------------------------------
External Vm was unable to communicate with the cloudstack managed VM.




After applying the fix
--------------------------




You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SudharmaJain/cloudstack cs-9165
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1246.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 #1246
----
commit 1bd12fce44d79a2825c4c78fbfe1183e04ce496d
Author: SudharmaJain <[email protected]>
Date: 2015-12-16T04:42:00Z
CLOUDSTACK-9165 unable to use reserved IP range in a network for external
VMs
----
> unable to use reserved IP range in a network for external VMs
> -------------------------------------------------------------
>
> Key: CLOUDSTACK-9165
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9165
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: sudharma jain
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)