Hi François,
On 03/08/2013 15:22, François Thiebolt wrote:
Hence, when I start to allocate VMs, they got the right IP starting
from 172.28.112.101 ... but when it's time to switch to the
172.28.113.xxx network, one of the VM get allocated the IP
172.28.112.255 (?!) and next one gets
ok lte's explain what is a valid network
/24 = 256 IP on a network and /23 = 512 ip on a network /22 = 1024 ip ...
one any network don't matter the size there are 2 ip's that can't be
used .. 1st ip of network and the last ip of network
in all cases on /24 /23 /22 or other bigger than /24
1st
Hello,
I've done the following setup for my production network :
NAME = production
TYPE = RANGED
BRIDGE = br0
NETWORK_ADDRESS = 172.28.112.0/23
IP_START= 172.28.112.101
IP_END = 172.28.113.240
Hence, when I start to allocate VMs, they got the right IP starting from
Hi François
.112.255 and .113.0 are perfectly valid IP addresses if you define a
.112.0/23 network.
If you don't want these addresses to be used you can mark them as RESERVED
in OpenNebula.
Simon
On Aug 3, 2013 9:22 AM, François Thiebolt francois.thieb...@irit.fr
wrote:
Hello,
I've done the
Hi Simon,
Thanks for the tip:
onevnet hold production 172.28.112.255
onevnet hold production 172.28.113.0
oneadmin@cloudmip[onevnet] onevnet show 0
VIRTUAL NETWORK 0 INFORMATION
ID : 0
NAME : production
USER : admin
GROUP : oneadmin
CLUSTER: -
Hello François,
In the subnet 172.28.112.0/23
Your network address is 172.28.112.0 and your broadcast address is
172.28.113.255; your usable range is 172.28.112.1-172.28.113.254.
172.28.112.255 and 172.28.113.0 are within the usable range.
I think your confusion is you IP range crosses a /24
