Subnetting an ISP Allocation for 100 Organizations (120.60.4.0/22)

Subnetting an ISP Allocation for 100 Organizations (120.60.4.0/22)

Verified Sources
Nov 3, 2026

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:

  1. Determine the size (number of addresses) of the original /22 block.
  2. Choose the correct CIDR prefix length for “8 addresses”.
  3. Allocate 100 equal sub-blocks sequentially.
  4. Compute how many addresses remain unused.

We’ll use standard CIDR facts: an IPv4 block with prefix length pp contains 232−p2^{32-p} 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 /p/p. The number of addresses in the block is:

232−p=232−22=210=10242^{32-p} = 2^{32-22} = 2^{10} = 1024

So, 120.60.4.0/22 contains 1024 addresses.

Key idea: since /22/22 means the subnet mask covers the first 22 bits, the block spans in steps of 210=10242^{10}=1024 addresses, which corresponds to 256 in the last octet times 4 in the third octet (because 1024=4×2561024 = 4 \times 256 addresses). Concretely, 120.60.4.0/22120.60.4.0/22 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:

232−p=8=23⇒32−p=3⇒p=292^{32-p} = 8 = 2^3 \Rightarrow 32-p = 3 \Rightarrow p = 29

So, the correct sub-block size is /29, because:

  • /29 contains 232−29=23=82^{32-29}=2^3=8 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

  1. 1
    Step 1

    Use /29/29 because 232−29=82^{32-29}=8 addresses per organization.

  2. 2
    Step 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, ...).

  3. 3
    Step 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.

  4. 4
    Step 4

    Allocated addresses = 100×8=800100 \times 8 = 800.

  5. 5
    Step 5

    Remaining = 1024−800=2241024 - 800 = 224.

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)
1120.60.4.0/29120.60.4.0 – 120.60.4.7
2120.60.4.8/29120.60.4.8 – 120.60.4.15
3120.60.4.16/29120.60.4.16 – 120.60.4.23
4120.60.4.24/29120.60.4.24 – 120.60.4.31
5120.60.4.32/29120.60.4.32 – 120.60.4.39
6120.60.4.40/29120.60.4.40 – 120.60.4.47
7120.60.4.48/29120.60.4.48 – 120.60.4.55
8120.60.4.56/29120.60.4.56 – 120.60.4.63
9120.60.4.64/29120.60.4.64 – 120.60.4.71
10120.60.4.72/29120.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: 0,8,16,…,2480, 8, 16, \dots, 248.
  • There are 256/8=32256/8 = 32 distinct /29 networks per third-octet value.
  • Since the original /22 spans third octets 4 through 7 (4 values), there are 4×32=1284 \times 32 = 128 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 kk (where k=1..32k=1..32) gets:
    • 120.60.4.(8times(k−1))(8\\times (k-1))/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 kk (where k=33..64k=33..64) gets:
    • 120.60.5.(8times(k−33))(8\\times (k-33))/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 kk (where k=65..96k=65..96) gets:
    • 120.60.6.(8times(k−65))(8\\times (k-65))/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 232−22=10242^{32-22}=1024 addresses. Since each /29 holds 8 addresses, the /22 contains 1024/8=1281024/8=128 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: 10241024
  • Addresses allocated: 100times8=800100 \\times 8 = 800

So remaining addresses:

1024−800=2241024 - 800 = 224

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: 224/8=28224/8 = 28 So there are 28 unused /29 sub-blocks remaining.

Subnetting Workflow for ISP Address Allocation

Start from 120.60.4.0/22

Step A

Compute total addresses: 232−22=10242^{32-22}=1024."

Match 8 addresses per org

Step B

Solve 232−p=8⇒p=292^{32-p}=8 \Rightarrow p=29, so use /29."

Allocate 100 consecutive /29 networks

Step C

Distribute through third octets 4,5,6 fully and 4 subnets in third octet 7."

Compute remaining capacity

Step D

Remaining addresses: 1024−100×8=2241024-100\times8=224."

Quick Checks & Edge Cases

Knowledge Check

Question 1 of 4
Q1Single choice

120.60.4.0/22 contains how many IPv4 addresses?