When adding a new IPv4 range in a vnet, it should be checked the IP spaces do not collide

[OpenNebulaProject]

---

Author Name: Andrés Pozo Muñoz (Andrés Pozo Muñoz)
Original Redmine Issue: 5064, https://dev.opennebula.org/issues/5064
Original Date: 2017-03-16

---

Hi,

when a new IPv4 range is added to a subnet, it's not checked the IPs in the range are not already in the vnet (nor in other vnet) so you don't end up with repeated IPs.

How to reproduce:

• Create a vnet and add an IPv4 range starting in 10.0.0.1
• Add to the same vNET a new range starting in 10.0.0.1

[OpenNebulaProject]

---

Original Redmine Comment
Author Name: Ruben S. Montero (@rsmontero)
Original Date: 2017-03-23T10:17:35Z

---

This is done on purpose. The idea is that you can have multiple AR's in the same VNET, this would be similar to a supernet. Now each AR may have even different VLAN_ID, so collisions in that case is not a problem.

I'm moving this as a request, to evaluate adding a warning.

[rsmontero]

We want to keep current behavior