Understanding Network Addresses and Their Role in Routing

When we assign an IP address to a device, like 1.2.3.4/24, it’s not just about identifying a single machine. That IP belongs to a network, and the address 1.2.3.0 in this case is known as the network address. But why do we reserve that address? What role does it play?

Let’s break it down.

---

What is a Network Address?

In any IP subnet, the first address (where all host bits are zero) is called the network address. It doesn’t point to a specific device. Instead, it represents the entire network.

For example:

• If you assign an IP like 1.2.3.4/24, the /24 tells us the subnet mask is 255.255.255.0.
• That means the network address is 1.2.3.0.
• The usable IP range is from 1.2.3.1 to 1.2.3.254, and 1.2.3.255 is the broadcast address.

---

Why is the Network Address Reserved?

We don’t assign the network address (1.2.3.0 in this case) to any device because it plays a special role in routing.

Here’s the key idea:

Routers and PCs use routing tables to decide where to send packets. But it’s not practical (or even possible) for a router to store every individual IP address in the world. Instead, they store network addresses, which represent a group of IPs.

---

Routing Table Example: PC with Two Network Interfaces

In this figure PC has two interfaces:
1. Interface eth1 with IP 1.2.3.1/24
2. Interface eth2 with IP 5.6.7.1/24

This PC’s routing table will automatically have:

• 1.2.3.0/24 → directly connected via eth1
• 5.6.7.0/24 → directly connected via eth2

Now imagine this PC wants to send a packet to 1.2.3.100. It doesn’t check if 1.2.3.100 is listed individually. Instead, it checks:

Does 1.2.3.100 fall under any known network?

Yes- it matches 1.2.3.0/24, so the packet is forwarded via eth1.

---

Why Not Store All Host IPs in Routing Tables?

That would make routing tables too large and slow.

Think about it:

• A /24 network contains 256 IPs.
• Storing each host separately would need 256 entries.
• But storing a single network address (1.2.3.0/24) covers all 256 IPs.

Now imagine how many entries would be needed for the entire internet if routers didn’t group IPs using network addresses. That’s why CIDR (Classless Inter-Domain Routing) and network address summarization are so important.

---

Summary

• Network addresses (like 1.2.3.0/24) represent a group of IPs.
• Routers use network addresses in their routing tables to simplify forwarding decisions.
• Devices don’t use the network address or broadcast address — those are reserved.
• Storing one entry per network keeps routing tables manageable and efficient.
  
  

---

Routing Table Example: Router with Direct and Indirectly Connected Networks

In this figure, we can see that all three routers — R1, R2, and R3 — are part of the same network 1.1.1.0/24, connected via a switch. This means they can directly reach each other using IPs within that subnet:

• R1 is configured with IP 1.1.1.1/24
• R2 with 1.1.1.2/24
• R3 with 1.1.1.3/24

Now look at the rest of the setup:

• R2 is also connected to another network: 2.2.2.0/24, which includes a few PCs through a switch.
• R3 is connected to a different network: 3.3.3.0/24, again with a switch and PCs.

From R1’s point of view, only the 1.1.1.0/24 network is directly reachable. But it still needs to know how to send packets to 2.2.2.0/24 and 3.3.3.0/24. That’s where its routing table comes in.

The routing table on R1 would look something like this:

• 1.1.1.0/24 → directly connected via R1’s local interface
• 2.2.2.0/24 → reachable via next-hop IP 1.1.1.2 (R2)
• 3.3.3.0/24 → reachable via next-hop IP 1.1.1.3 (R3)

This setup shows how routers use network addresses, not individual host IPs, to forward packets. When R1 receives a packet destined for, say, 2.2.2.50, it checks the routing table and finds that it belongs to 2.2.2.0/24, which is routed via R2.

---