Subnetting an ISP Allocation for 100 Organizations (120.60.4.0/22)
We are given an ISP address block keyword block of 120.60.4.0/22. The ISP must split it into sub-blocks sized so that each of 100 organizations receives just eight addresses.
We will:
- Determine the size (number of addresses) of the original /22 block.
- Choose the correct CIDR prefix length for “8 addresses”.
- Allocate 100 equal sub-blocks sequentially.
- Compute how many addresses remain unused.
We’ll use standard CIDR facts: an IPv4 block with prefix length contains addresses, and for subnet boundaries the increment in the last octet follows the subnet size.
CIDR Subnetting Basics (IPv4) - Prefix Length, Block Size, Address Ranges
1) Compute how many addresses are in 120.60.4.0/22
For IPv4, a CIDR block keyword is written as . The number of addresses in the block is:
So, 120.60.4.0/22 contains 1024 addresses.
Key idea: since means the subnet mask covers the first 22 bits, the block spans in steps of addresses, which corresponds to 256 in the last octet times 4 in the third octet (because addresses). Concretely, covers:
- from 120.60.4.0
- through 120.60.7.255
Thus, the usable range is: 120.60.4.0 – 120.60.7.255.
2) Find the CIDR prefix length that gives exactly 8 addresses
We need a sub-block with 8 addresses. For IPv4:
So, the correct sub-block size is /29, because:
- /29 contains addresses.
keyword Subnet mask for /29 is 255.255.255.248 (standard).
Therefore each organization should be assigned a /29 network: 8 total addresses per organization.
Designing the 100 sub-blocks (/29) inside 120.60.4.0/22
- 1Step 1
Use because addresses per organization.
- 2Step 2
A /29 block spans 8 addresses, so the next /29 starts 8 addresses later. In the last octet this means increments of 8 (e.g., .0, .8, .16, ...).
- 3Step 3
Starting from 120.60.4.0/29, the block boundaries move by +8 in the last octet. After .248/29, the next starts at 120.60.(next-third-octet).0/29.
- 4Step 4
Allocated addresses = .
- 5Step 5
Remaining = .
3) Sub-block design (slash notation for each sub-block)
Each organization gets one /29. The first few /29 networks from the base block are:
| Org # | Sub-block (slash notation) | Address range (8 addresses) |
|---|---|---|
| 1 | 120.60.4.0/29 | 120.60.4.0 – 120.60.4.7 |
| 2 | 120.60.4.8/29 | 120.60.4.8 – 120.60.4.15 |
| 3 | 120.60.4.16/29 | 120.60.4.16 – 120.60.4.23 |
| 4 | 120.60.4.24/29 | 120.60.4.24 – 120.60.4.31 |
| 5 | 120.60.4.32/29 | 120.60.4.32 – 120.60.4.39 |
| 6 | 120.60.4.40/29 | 120.60.4.40 – 120.60.4.47 |
| 7 | 120.60.4.48/29 | 120.60.4.48 – 120.60.4.55 |
| 8 | 120.60.4.56/29 | 120.60.4.56 – 120.60.4.63 |
| 9 | 120.60.4.64/29 | 120.60.4.64 – 120.60.4.71 |
| 10 | 120.60.4.72/29 | 120.60.4.72 – 120.60.4.79 |
Continuing the pattern:
- Within a fixed third octet (here 4), the last octet starts at 0 and increases by 8: .
- There are distinct /29 networks per third-octet value.
- Since the original /22 spans third octets 4 through 7 (4 values), there are total /29 subnets available in the whole /22.
So to allocate 100 subnets:
- Allocate 32 subnets in third octet 4 (Org 1–32)
- Allocate 32 subnets in third octet 5 (Org 33–64)
- Allocate 32 subnets in third octet 6 (Org 65–96)
- Allocate the remaining 4 subnets in third octet 7 (Org 97–100)
Exact slash notation blocks for Org 1–100
To keep this readable while still exact, use the following enumeration rules:
For third octet = 4 (Org 1–32):
- Org (where ) gets:
- 120.60.4./29
So Org 1–32 are:
- 120.60.4.0/29, 120.60.4.8/29, 120.60.4.16/29, ..., 120.60.4.248/29
For third octet = 5 (Org 33–64):
- Org (where ) gets:
- 120.60.5./29
So Org 33–64 are:
- 120.60.5.0/29, 120.60.5.8/29, 120.60.5.16/29, ..., 120.60.5.248/29
For third octet = 6 (Org 65–96):
- Org (where ) gets:
- 120.60.6./29
So Org 65–96 are:
- 120.60.6.0/29, 120.60.6.8/29, 120.60.6.16/29, ..., 120.60.6.248/29
For third octet = 7 (Org 97–100): Only the first 4 /29 blocks in that third octet:
- Org 97: 120.60.7.0/29
- Org 98: 120.60.7.8/29
- Org 99: 120.60.7.16/29
- Org 100: 120.60.7.24/29
type="tip" title="Pro Tip: Count /29 subnets correctly" content="A /22 contains addresses. Since each /29 holds 8 addresses, the /22 contains total /29 subnets. That’s why we can fully allocate 100 organizations and still have unused subnets."
type="warning" title="Allocation must match boundaries" content="Each /29 network start must align to multiples of 8 in the last octet (e.g., .0, .8, .16, ...). If you pick a non-aligned address like .6, the block wouldn’t be a valid /29 network boundary."
Address Utilization
How many IPv4 addresses are allocated vs. left unused.
4) How many addresses are still available after these allocations?
We computed:
- Original addresses in /22:
- Addresses allocated:
So remaining addresses:
Therefore, 224 addresses are still available inside 120.60.4.0/22 after allocating 100 organizations with /29 blocks.
Additionally, since each /29 uses 8 addresses, the number of unused /29 subnets is: So there are 28 unused /29 sub-blocks remaining.
Subnetting Workflow for ISP Address Allocation
Start from 120.60.4.0/22
Step ACompute total addresses: ."
Match 8 addresses per org
Step BSolve , so use /29."
Allocate 100 consecutive /29 networks
Step CDistribute through third octets 4,5,6 fully and 4 subnets in third octet 7."
Compute remaining capacity
Step DRemaining addresses: ."
Quick Checks & Edge Cases
Knowledge Check
120.60.4.0/22 contains how many IPv4 addresses?