[one-users] annoying IP allocation

[Ionut Popovici]

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 ip is last octet from ip group is 0
and last ip octet is 255
if u go less that /24 u will have diference
in your case ip 172.28.112.0/23 the ip that can be used are 172.28.112.1 
to 172.28.113.254
172.28.112.0 -is 1st ip aka network ip
172.28.113.0 - is last ip aka brodcast ip
in some cases if the ip are routers tru network sometime routed protocol 
can brake larger netwoks in less networks and this will make 
172.28.112.255 and 172.28.113.0 not to work but i don't think is your case.
Good luck .

Sorry i'm not native english speeker
On 8/4/2013 11:36 PM, Giovanni Toraldo wrote:
> 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 172.28.113.0 ?!?!
> Why this looks strange to you? If you have a network larger than /24,
> there is no problem on using .255 or .0 adresses, and OpenNebula has no
> reasons to simply skip them.
>
> Cheers,