Backlog #5064

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

Added by Andrés Pozo Muñoz over 4 years ago. Updated over 4 years ago.

Status:PendingStart date:03/16/2017
Priority:LowDue date:
Assignee:-% Done:


Target version:-



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 * Add to the same vNET a new range starting in

Captura de pantalla 2017-03-16 a las 17.11.59.png (40.5 KB) Andrés Pozo Muñoz, 03/16/2017 04:19 PM


#1 Updated by Ruben S. Montero over 4 years ago

  • Tracker changed from Bug to Request
  • Category set to Sunstone

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.

#2 Updated by Miguel Ángel Álvarez Cabrerizo over 4 years ago

  • Tracker changed from Request to Backlog
  • Priority changed from Normal to Low

Also available in: Atom PDF