Hi, The NETWORK_SIZE is used to compute the network mask for 202 addresses (including network and broadcast) you need 8 bits so 24 bits for the network mask. This gives you a network 10.243.19.0/24, so the first IP is 10.243.19.1and OpenNebula will give you IPs from 10.243.19.1 to 10.243.19.200
Cheers Ruben On Wed, Apr 27, 2011 at 5:08 PM, Lars Kellogg-Stedman <l...@seas.harvard.edu > wrote: > Hello all, > > I have a network defined like this: > > NAME="Cloud Private" > TYPE=RANGED > BRIDGE=br619 > GATEWAY=10.243.19.1 > NETWORK_ADDRESS=10.243.19.20 > NETWORK_SIZE=200 > > I would expect this to allocate addresses in the range 10.243.19.20 - > 10.243.19.220. However, if I create a VM from this description: > > CPU = 1 > MEMORY = 1024 > DISK = [ image = "Basic Server" ] > NIC = [ NETWORK = "Cloud Private" ] > GRAPHICS = [ > type = "vnc", > listen = "0.0.0.0" > ] > > It gets a lease for 10.243.19.1: > > $ onevnet show 'Cloud Private' > VIRTUAL NETWORK 1 INFORMATION > ID: : 1 > UID: : 0 > PUBLIC : N > > VIRTUAL NETWORK TEMPLATE > BRIDGE=br619 > GATEWAY=10.243.19.1 > NAME=Cloud Private > NETWORK_ADDRESS=10.243.19.20 > NETWORK_SIZE=200 > TYPE=RANGED > > LEASES INFORMATION > LEASE=[ IP=10.243.19.1, MAC=5e:a5:0a:f3:13:01, USED=1, VID=13 ] > > How do I fix this? Do I simply not understand how ranged networks > work? Thanks for your help, > > -- > Lars Kellogg-Stedman <l...@seas.harvard.edu> > Senior Technologist > Harvard University SEAS > Academic and Research Computing (ARC) > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > -- Dr. Ruben Santiago Montero Associate Professor (Profesor Titular), Complutense University of Madrid URL: http://dsa-research.org/doku.php?id=people:ruben Weblog: http://blog.dsa-research.org/?author=7
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
