You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Abhinav Roy (JIRA)" <ji...@apache.org> on 2013/06/24 10:34:19 UTC
[jira] [Closed] (CLOUDSTACK-1748) IP Reservation results in
reserving the broadcast IP of the network as well
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Abhinav Roy closed CLOUDSTACK-1748.
-----------------------------------
> IP Reservation results in reserving the broadcast IP of the network as well
> ---------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1748
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1748
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Network Controller
> Affects Versions: 4.2.0
> Reporter: Abhinav Roy
> Assignee: Saksham Srivastava
> Fix For: 4.2.0
>
>
> Description :
> ========================
> Ip reservation results in reservation of broadcast ip of the network as well.
> Steps :
> =======================
> 1. Create a guest network with CIDR 10.1.1.0/24
> 2. Make IP reservation with 10.1.1.0/25
> Expected result :
> ======================
> The broadcast IP of the guest CIDR 10.1.1.0/25 is 10.1.1.127 , now this IP should not be reserved.
> Address: 10.1.1.0 00001010.00000001.00000001.0 0000000
> Netmask: 255.255.255.128 = 25 11111111.11111111.11111111.1 0000000
> Wildcard: 0.0.0.127 00000000.00000000.00000000.0 1111111
> =>
> Network: 10.1.1.0/25 00001010.00000001.00000001.0 0000000 (Class A)
> Broadcast: 10.1.1.127 00001010.00000001.00000001.0 1111111
> HostMin: 10.1.1.1 00001010.00000001.00000001.0 0000001
> HostMax: 10.1.1.126 00001010.00000001.00000001.0 1111110
> Hosts/Net: 126 (Private Internet)
> Observation :
> ======================
> The broadcast IP of the guest CIDR gets reserved as well
> <listnetworksresponse cloud-stack-version="4.2.0-SNAPSHOT"><count>1</count><network><id>d34f885d-9f19-4d0e-92eb-95f0d33bcaea</id><name>N-2</name><displaytext>n2</displaytext><broadcastdomaintype>Vlan</broadcastdomaintype><traffictype>Guest</traffictype><gateway>10.1.1.1</gateway><netmask>255.255.255.0</netmask><cidr>10.1.1.0/25</cidr><networkcidr>10.1.1.0/24</networkcidr><reservediprange>10.1.1.127-10.1.1.254</reservediprange><zoneid>499a59a4-e42f-422b-99ec-0fb682e8b2d1</zoneid><zonename>Zone-1</zonename><networkofferingid>3f320aaa-5128-49a7-8a70-8cd975d6fe17</networkofferingid><networkofferingname>DefaultIsolatedNetworkOfferingWithSourceNatService</networkofferingname><networkofferingdisplaytext>Offering for Isolated networks with Source Nat service enabled</networkofferingdisplaytext><networkofferingavailability>Required</networkofferingavailability><issystem>false</issystem><state>Implemented</state>
> Same observation is made when the guest CIDR is 10.1.1.0/26 , 10.1.1.0/27 , 10.1.1.0/28 etc
> Address: 10.1.1.0 00001010.00000001.00000001.00 000000
> Netmask: 255.255.255.192 = 26 11111111.11111111.11111111.11 000000
> Wildcard: 0.0.0.63 00000000.00000000.00000000.00 111111
> =>
> Network: 10.1.1.0/26 00001010.00000001.00000001.00 000000 (Class A)
> Broadcast: 10.1.1.63 00001010.00000001.00000001.00 111111
> HostMin: 10.1.1.1 00001010.00000001.00000001.00 000001
> HostMax: 10.1.1.62 00001010.00000001.00000001.00 111110
> Hosts/Net: 62 (Private Internet)
> <listnetworksresponse cloud-stack-version="4.2.0-SNAPSHOT"><count>1</count><network><id>01a2dcaa-f21d-4096-8b24-755e74d67fa5</id><name>N-1</name><displaytext>N-1</displaytext><broadcastdomaintype>Vlan</broadcastdomaintype><traffictype>Guest</traffictype><gateway>10.1.1.1</gateway><netmask>255.255.255.0</netmask><cidr>10.1.1.0/26</cidr><networkcidr>10.1.1.0/24</networkcidr><reservediprange>10.1.1.63-10.1.1.254</reservediprange><zoneid>499a59a4-e42f-422b-99ec-0fb682e8b2d1</zoneid><zonename>Zone-1</zonename><networkofferingid>3f320aaa-5128-49a7-8a70-8cd975d6fe17</networkofferingid>
--
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