[
https://issues.apache.org/jira/browse/CLOUDSTACK-9086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054139#comment-15054139
]
ASF subversion and git services commented on CLOUDSTACK-9086:
-------------------------------------------------------------
Commit 66d7f413e8e67c83727ca159495df8f4a8dc1bd0 in cloudstack's branch
refs/heads/master from [~remibergsma]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=66d7f41 ]
Merge pull request #1188 from kansal/CLOUDSTACK-9086
CLOUDSTACK-9086: ACS allows to create isolated networks with invalide gateway
IP address - Fixed and Test cases added
Problem: There was no check for the network and broadcast IP addresses in the
case where we provide the gateway and netmask while creating the isolated
network. As a result the provided IP gets assigned to the eth0 interface of the
VR.
Note: This is in continuation of PR #1125 which I closed.
* pr/1188:
CLOUDSTACK-9086: ACS allows to create isolated networks with invalide gateway
IP address - Fixed and Test cases added
Signed-off-by: Remi Bergsma <[email protected]>
> ACS allows to create isolated networks with invalid gateway IP address
> ----------------------------------------------------------------------
>
> Key: CLOUDSTACK-9086
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9086
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Kshitij Kansal
> Assignee: Kshitij Kansal
>
> When entering invalid combination no check is performed anymore and VR is
> created with invalid interface. Of course, nothing works in the isolated
> network. For example, you are allowed to create network with 172.16.21.0 IP
> address for GW and 255.255.255.0 for SM - this address is not valid, however
> it is accepted and even used in VR. One more example - 192.168.255.255 for GW
> address and 255.255.255.0 for SM.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
