LogoفارسیFA

IPv4 Addressing Fundamentals: Structure, Classes, and Subnet Masks

Every device on an IPv4 network needs a unique address that encodes both which network it belongs to and its specific identity within that network. This article explains the structure of an IPv4 address, the historical concept of address classes, how subnet masks define the boundary between network and host portions, and the essential commands for viewing and verifying IP addressing on a Cisco device.

IPv4 AddressingSubnet MaskNetwork and Host Portion

~4 min read · Updated Sep 9, 2026

The Structure of an IPv4 Address

An IPv4 Address is a 32-bit number, conventionally written as four decimal numbers separated by dots (called Dotted-Decimal Notation), with each number representing one 8-bit group called an Octet.

Example address: 192.168.1.10

Binary breakdown:
192       .168      .1        .10
11000000  .10101000 .00000001 .00001010

Each octet ranges from 0 to 255,
since 8 bits can represent 2^8 = 256 distinct values

Every IPv4 address logically splits into two parts: a Network Portion, identifying which network the device belongs to, and a Host Portion, identifying the specific device within that network. Where exactly this split occurs is determined by the subnet mask, discussed below.

Historical Address Classes

IPv4 addressing originally used a rigid Classful system, dividing the address space into classes with fixed network/host boundaries. While largely obsolete for modern network design, this classification still influences default behaviors and terminology used throughout networking today.

Class A: 1.0.0.0   - 126.255.255.255  (default mask /8)
Class B: 128.0.0.0 - 191.255.255.255  (default mask /16)
Class C: 192.0.0.0 - 223.255.255.255  (default mask /24)
Class D: 224.0.0.0 - 239.255.255.255  (multicast, not for hosts)
Class E: 240.0.0.0 - 255.255.255.255  (reserved, experimental)

Modern networks almost universally use Classless addressing instead, discussed later in this series regarding VLSM and CIDR, which allows the network/host boundary to fall anywhere rather than being fixed by class — but understanding the classful ranges remains useful for recognizing default behaviors in older configurations and certain protocol defaults.

The Subnet Mask: Defining Network and Host Boundaries

A Subnet Mask is a 32-bit value that marks which bits of an IP address belong to the network portion (represented by binary 1s) and which belong to the host portion (represented by binary 0s).

Address:      192.168.1.10
Subnet Mask:  255.255.255.0
Binary mask:  11111111.11111111.11111111.00000000

The first 24 bits (three full octets) are network bits,
the last 8 bits are host bits

This is commonly written in CIDR notation as /24,
indicating 24 network bits

Performing a bitwise AND between an address and its subnet mask reveals the Network Address — the address representing the network itself, not any specific host on it.

192.168.1.10   AND   255.255.255.0
= 192.168.1.0    (the network address)

This means devices with addresses 192.168.1.1
through 192.168.1.254 all belong to the same
192.168.1.0/24 network

Special Addresses Within Every Subnet

Within any subnet, two addresses are reserved and cannot be assigned to a host device.

For the 192.168.1.0/24 network:

Network Address:   192.168.1.0   (all host bits = 0)
                    identifies the network itself

Broadcast Address: 192.168.1.255 (all host bits = 1)
                    reaches every device on that subnet

Usable host range: 192.168.1.1 - 192.168.1.254

Sending a packet to the broadcast address delivers it to every device on that local subnet simultaneously — a mechanism used by protocols like ARP and DHCP, which require reaching all devices before a specific unicast address is even known.

Configuring and Verifying IP Addressing on a Cisco Device

Router(config)# interface gigabitethernet 0/0
Router(config-if)# ip address 192.168.1.1 255.255.255.0
Router(config-if)# no shutdown

Router# show ip interface brief

Interface              IP-Address      Status    Protocol
GigabitEthernet0/0      192.168.1.1     up        up
GigabitEthernet0/1      unassigned      down      down

show ip interface brief is one of the most frequently used verification commands in daily operations, providing an immediate summary of which interfaces have addresses assigned and whether they are operationally up — the first command most administrators run when checking a device's basic connectivity status.

Private Versus Public Addresses

Certain address ranges are reserved by standard for Private use within internal networks, never routed across the public internet directly.

Private address ranges (RFC 1918):
10.0.0.0        - 10.255.255.255    (10.0.0.0/8)
172.16.0.0      - 172.31.255.255    (172.16.0.0/12)
192.168.0.0     - 192.168.255.255   (192.168.0.0/16)

These ranges are used extensively inside homes and enterprises specifically because their limited global supply of public IPv4 addresses made reusing the same private ranges across countless separate networks necessary — a device using a private address relies on Network Address Translation, covered later in this series, to communicate with the public internet.

Why IPv4 Addressing Fundamentals Underlie Everything That Follows

Every subnetting calculation, routing protocol, and access control list covered later in this series operates directly on the network and host address structure introduced here. Fluently converting between dotted-decimal and binary representations, and immediately recognizing which addresses belong to the same subnet, is a foundational skill that every subsequent networking topic assumes as a prerequisite.

Written & researched by Dr. Shahin Siami

Related Articles

OSPF Fundamentals: Link-State Routing Explained

OSPF is the most widely deployed interior routing protocol in enterprise networks, using a fundamentally different approach than simply exchanging routing tables between neighbors. This article explains what a link-state protocol actually is, how OSPF routers become neighbors and build a shared topology database, how the cost metric determines the best path, and the essential commands for configuring and verifying single-area OSPF.

Continue

Network Address Translation: Sharing Public IP Addresses

The limited supply of public IPv4 addresses made it impossible for every device worldwide to have its own globally unique address, and Network Address Translation solved this by letting many private devices share a small number of public addresses. This article explains the three main NAT types, walks through configuring static NAT, dynamic NAT, and PAT on a Cisco router, and covers the essential commands for verifying active translations.

Continue

Access Control Lists: Filtering Traffic on Cisco Routers

Access Control Lists let a router or switch selectively permit or deny traffic based on source, destination, and protocol information, forming the foundation of basic network security and traffic filtering. This article explains how ACLs process traffic sequentially, covers the difference between standard and extended ACLs, walks through wildcard mask calculation, and explains critical placement rules that determine whether an ACL works as intended.

Continue

DHCP and DNS: Automatic Addressing and Name Resolution

Manually configuring an IP address on every device does not scale, and remembering numeric IP addresses for every service is impractical, which is why DHCP and DNS exist as essential supporting services in nearly every network. This article explains how DHCP automatically assigns IP addressing information, covers configuring a Cisco device as a DHCP server or relay agent, and explains how DNS resolves human-readable names into IP addresses.

Continue

Inter-VLAN Routing: Connecting VLANs with Router-on-a-Stick and SVIs

VLANs isolate broadcast domains from each other at Layer 2, but real applications still need devices in different VLANs to communicate, which requires routing between them at Layer 3. This article explains the legacy router-on-a-stick approach using subinterfaces, the modern and more scalable Switch Virtual Interface approach on Layer 3 switches, and the essential configuration and verification commands for both.

Continue

EtherChannel: Combining Multiple Links Into One Logical Connection

Instead of choosing between redundancy and bandwidth, EtherChannel combines multiple physical links into a single logical connection that provides both simultaneously, without Spanning Tree blocking any of the links. This article explains how EtherChannel bundles ports together, compares the PAgP and LACP negotiation protocols used to form a bundle safely, and covers the essential configuration and verification commands.

Continue
Previous ArticleNext Article