Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8A016CF26 for ; Tue, 25 Jun 2013 11:54:21 +0000 (UTC) Received: (qmail 44166 invoked by uid 500); 25 Jun 2013 11:54:21 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 44105 invoked by uid 500); 25 Jun 2013 11:54:20 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 44096 invoked by uid 500); 25 Jun 2013 11:54:20 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 44092 invoked by uid 99); 25 Jun 2013 11:54:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Jun 2013 11:54:20 +0000 Date: Tue, 25 Jun 2013 11:54:20 +0000 (UTC) From: "Sanjeev N (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Closed] (CLOUDSTACK-2511) Multiple_Ip_Ranges: Adding guest ip range in subset/superset to existing CIDR is allowed MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjeev N closed CLOUDSTACK-2511. --------------------------------- Verified with latest build from master-6-17-stable branch. Works fine. > Multiple_Ip_Ranges: Adding guest ip range in subset/superset to existing CIDR is allowed > ---------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-2511 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2511 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: Management Server > Affects Versions: 4.2.0 > Environment: Build from master branch:CloudStack-non-OSS-MASTER-340-rhel6.3.tar.gz > Reporter: Sanjeev N > Assignee: Bharat Kumar > Priority: Critical > Fix For: 4.2.0 > > > Adding guest ip range in subset/superset to existing CIDR is allowed, but as per the FS adding guest ip range subset or super set to existing subnet should fail. > Repro steps: > =========== > 1.Bring up CS in basic zone with xenserver 6.1 > 2.Add ip range as follows: > gw:10.147.40.1 > Netmask: 255.255.255.0 > IP Range: 10.147.40.2-10.147.40.10 > 3.Try to add another guest IP range super set to exiting subnet > eg: gw 10.147.40.1, Netmask 255.255.254.0 > IP Range: 10.147.40.20-10.147.40.30 > 4.Try to add another guest IP range subset to existing subnet > eg: gw 10.147.40.1, Netmask 255.255.255.128 > IP Range 10.147.40.40-10.147.40.50 > Expected Behaviour: > ================ > Though the new ip range added at step3 falls under existing subnet, adding it should fails since its subnet is superset to existing subnet. > Similarly new ip range at step4 falls under existing subnet, but adding it should fail since its subnet is subset to existing subnet. > Actual Behaviour: > =============== > Adding ip range in subset/super set to existing subnet is not failing. > Observations: > =========== > If the new ip range is subset/superset to exiting subnet and does not fall under the exiting subnet then only CS does not allow adding that ip range. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira