IP Addressing and Subnetting Explained — CIDR, Masks and Real-World Design

Every packet of data travelling across the internet — your Netflix stream, that Slack message, the API call your app just made — is stamped with a source and destination IP address before it leaves your machine. Without IP addressing, the internet is just a room full of computers shouting into the void. It's the foundational contract that makes global communication possible, and understanding it deeply separates engineers who configure networks from engineers who truly understand them.

The problem IP addressing solves is deceptively simple: how do you uniquely identify billions of devices and route traffic between them efficiently? The naive answer — give every device a globally unique number — breaks down immediately when you realise IPv4 only has about 4.3 billion addresses and we blew past that years ago. Subnetting, CIDR, and private address ranges are the engineering solutions to that scarcity, and they're still baked into every cloud VPC, Kubernetes cluster, and corporate network you'll ever touch.

By the end of this article you'll be able to read a CIDR block like 192.168.1.0/24 and instantly know how many hosts it supports, how to split it into smaller subnets, and why that matters when you're designing a VPC on AWS or debugging a routing issue in production. You'll also walk away with the mental model and Python code to calculate subnets programmatically — a skill that'll save you from subnet calculators forever.

What is IP Addressing and Subnetting?

IP Addressing and Subnetting is a core concept in CS Fundamentals. Rather than starting with a dry definition, let's see it in action and understand why it exists.

// TheCodeForge — IP Addressing and Subnetting example
// Always use meaningful names, not x or n
public class ForgeExample {
    public static void main(String[] args) {
        String topic = "IP Addressing and Subnetting";
        System.out.println("Learning: " + topic + " 🔥");
    }
}

Frequently Asked Questions