Azure Subnet address range issue

Question

Hello, This is bonah koo.
I think I got some bugs in Azure Vnet, especially on Subnet prefix.
ok. here is the thing.
I assigned vnet address range to 10.2.0.0/16 , and this means I can use 255*255 for sure(which is 10.2.0.0 ~ 10.2.255.255)
And I am trying to subnetting this thing to 3 subnet.
Let's say, snet-1, snet-2, snet-3.

Here is the problem start. let's give you some examples here.

1. Assigning same subnet bits.
I assigned subnet something like this.

snet-1 : 10.2.0.0/26,
snet-2 : 10.2.0.64/26
snet-3 : 10.2.0.128/26

and this test is working absolutely fine.

2. Assigning diffrenet subnet bits(descending)
I assigned subnet something like this.

snet-1 : 10.2.0.0/25
snet-2 : 10.2.0.128/26
snet-3 : 10.2.0.192/26

it works perfectly fine.

3. Assigning different subnet bits(ascending)

here is the problem starts.
I am trying to assign subnet something like this.
snet-1 : 10.2.0.0/27
snet-2 : 10.2.0.32/26
snet-3 : 10.2.0.96/26

and it doesn't work at all. and it says something like this.

10.2.0.32/26 is not a valid CIDR block. Use 10.2.0.0/26 instead.
This subnet address prefix overlaps with '10.2.0.0/27'.

what the hack? I think no issue is here, but somehow Azure calculator(decide the address range I think?)is something logical problem.

4. this one is also shocking test.
I assigned subnet something like this.
snet-1 : 10.2.0.0/27
snet-2 : 10.2.0.32/28
snet-3 : 10.2.0.128/25

and it works fine.

but if I assign
snet-1 : 10.2.0.0/27
snet-2 : 10.2.0.32/28
snet-3 : 10.2.0.48/27

It doesn't work.

somebody help me with this? or is it Azure bug issue?

Thanks

Answer 1

This was my mistake...

The reason that it didn't work is
26bit can subnet only
10.2.0.0/26, 10.2.0.64/26, 10.2.0.128/26, 10.2.0.192/26 ...

So, the way I gave this something like 10.2.0.32/26 didn't make sense at all..

Maybe this could help someone later, I will leave this here.
Thanks