When adding a new IPv4 range in a vnet, it should be checked the IP spaces do not collide
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
#1 Updated by Ruben S. Montero about 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.