Greetings, Tech Talkers!
This is Tor from Tors Tech Talk, your trusted network engineering uplink!
Today, we’re diving into one of the most fundamental and, let’s be honest, sometimes intimidating topics in networking—IPv4 addressing and subnetting. Whether you’re setting up a small home network or configuring a complex enterprise environment, understanding how to configure and verify IPv4 addresses and properly subnet your network is a must-have skill.
In this article, we’ll break down the essentials of configuring IPv4 addresses, walk through subnetting step-by-step, and then finish with methods to verify your configurations. By the end of this, you’ll be subnetting like a pro and never second-guessing an IP address range again!
Let’s get into it!
IPv4 Addressing Fundamentals: A Refresher
Before we jump into configuration and subnetting, let’s quickly revisit what an IPv4 address is. IPv4 (Internet Protocol version 4) addresses are 32-bit numbers, typically written in dotted decimal notation, which looks something like this: 192.168.1.1.
The 32 bits are divided into four octets (8 bits each), with each octet separated by a dot. The value of each octet ranges from 0 to 255, which means the total possible IPv4 address space is 2^32, or roughly 4.3 billion unique addresses.
IPv4 Address Classes:
Class A: 0.0.0.0 to 127.255.255.255 (16 million addresses per network)
Class B: 128.0.0.0 to 191.255.255.255 (65,536 addresses per network)
Class C: 192.0.0.0 to 223.255.255.255 (254 addresses per network)
Most modern networks use Classless Inter-Domain Routing (CIDR), but it’s still important to understand these classes as they form the basis for subnetting.
Subnetting: Breaking Down Networks for Efficiency
Subnetting is the process of dividing a larger network into smaller, more manageable pieces. By doing this, you can improve network efficiency, enhance security, and reduce broadcast traffic.
To subnet a network, we essentially “borrow” bits from the host portion of an IP address to create additional network segments. This is accomplished by adjusting the subnet mask, which tells us how many bits are allocated for the network and how many for the hosts.
Subnet Mask Basics:
The subnet mask is a 32-bit number that distinguishes the network portion of an IP address from the host portion. It’s typically written in dotted decimal format, just like an IP address (e.g., 255.255.255.0). Alternatively, it can be written using CIDR notation (e.g., /24 for 255.255.255.0).
/8 (255.0.0.0) – Class A default
/16 (255.255.0.0) – Class B default
/24 (255.255.255.0) – Class C default
How to Subnet: A Step-by-Step Example
Let’s walk through a real-world subnetting example.
Scenario: You’ve been given the network 192.168.10.0/24 and asked to subnet it into four smaller subnets for different departments in your office.
Step 1: Understand the Current Network
The IP range 192.168.10.0/24 has 256 total addresses (2^8 = 256, because 24 bits are reserved for the network, leaving 8 bits for the hosts).
In /24, the subnet mask is 255.255.255.0, meaning there are 254 usable host addresses (since the first address is the network address and the last is the broadcast address).
Step 2: Determine How Many Subnets You Need
You need four subnets, so we need to borrow bits from the host portion to create more networks.
Using the formula 2^n ≥ required subnets, where n is the number of bits to borrow, we find that 2^2 = 4, meaning we need to borrow 2 bits from the host portion.
Step 3: Calculate the New Subnet Mask
If we borrow 2 bits, the new subnet mask becomes /26, which translates to 255.255.255.192. This gives us four subnets, each with 64 total addresses (62 usable).
Step 4: Divide the Network into Subnets Here are the four new subnets:
Subnet 1: 192.168.10.0/26 (usable range: 192.168.10.1 to 192.168.10.62, broadcast: 192.168.10.63)
Subnet 2: 192.168.10.64/26 (usable range: 192.168.10.65 to 192.168.10.126, broadcast: 192.168.10.127)
Subnet 3: 192.168.10.128/26 (usable range: 192.168.10.129 to 192.168.10.190, broadcast: 192.168.10.191)
Subnet 4: 192.168.10.192/26 (usable range: 192.168.10.193 to 192.168.10.254, broadcast: 192.168.10.255)
By breaking the network into these four subnets, you’ve effectively created four smaller networks, each capable of handling up to 62 hosts.
Subnetting Cheat Sheet:
/30 = 4 total addresses, 2 usable
/29 = 8 total addresses, 6 usable
/28 = 16 total addresses, 14 usable
/27 = 32 total addresses, 30 usable
/26 = 64 total addresses, 62 usable
/25 = 128 total addresses, 126 usable
For the full table check this resource out. I recommend you bookmark it for future reference.
Configuring IPv4 Addressing on Cisco Devices
Now that we’ve subnetted our network, let’s move on to configuring IPv4 addresses on Cisco devices. We’ll use a Cisco router as our example.
Assigning an IP Address to an Interface:
To configure an IPv4 address on an interface, follow these steps:
1. Enter global configuration mode:
Router> enableRouter# configure terminal2. Access the interface you want to configure (e.g., GigabitEthernet 0/0):
Router(config)# interface GigabitEthernet0/03. Assign the IP address and subnet mask to the interface:
Router(config-if)# ip address 192.168.10.1 255.255.255.1924. Enable the interface (bring it up):
Router(config-if)# no shutdown5. Exit the interface configuration mode:
Router(config-if)# exitVerifying the Configuration:
Once you’ve configured the interface, use the following commands to verify the settings:
Show IP Interface Brief:
Router# show ip interface briefThis command displays a summary of all interfaces, including their IP addresses and operational statuses.
Show Running-Config:
Router# show running-configThis will display the current configuration, allowing you to double-check the assigned IP addresses and subnet masks.
Verifying IPv4 Addressing on Hosts
Configuring the network devices is one thing, but verifying the addressing on your client devices is just as important. Let’s look at how to verify the IP address on common operating systems.
Windows:
1. Open Command Prompt:
ipconfigThis command will display the current IP configuration, including the IP address, subnet mask, and default gateway.
Linux/macOS:
On Linux and macOS, the ifconfig or ip addr command provides a similar output, showing the IP address and subnet mask for each interface.
1. Open Terminal:
ifconfigFor some Linux systems, you may need to use
ip addr6. Best Practices for IPv4 Addressing and Subnetting
To make the most of your IPv4 addressing, follow these best practices:
1. Use Private IP Addresses for Internal Networks: Always use private IP address ranges (RFC1918) for internal networks:
10.0.0.0/8
172.16.0.0/12
192.168.0.0/16
These ranges are reserved for private use and won’t route on the public internet, which ensures your internal traffic stays within your network.
2. Plan for Growth: When designing your network, always plan for future growth. Subnet your network with enough room to add additional hosts without having to redesign the entire addressing scheme.
3. Document Your Subnetting: Keep detailed records of your subnets, including which IP ranges are assigned to each department or function. This helps prevent address conflicts and makes troubleshooting much easier.
4. Avoid Using /30 for Point-to-Point Links When Possible: While /30 subnets (which provide 2 usable IP addresses) are traditionally used for point-to-point links, /31 subnets can often be a better choice in environments that support them, allowing you to maximize IP address utilization.
5. Verify Configuration: After configuring your devices, always verify your settings using show commands and by testing connectivity between devices (for example, with the ping command).
6. Use Subnetting Tools: When in doubt, use subnetting calculators or tools to verify your configurations and ensure you’re calculating address ranges correctly. There’s no harm in double-checking!
My personal favorite is the Boson Subnet Calculator. Book mark it!
Wrapping It Up
And there you have it, Tech Talkers—IPv4 addressing and subnetting demystified! Subnetting might seem complex at first, but with practice, it becomes second nature. By understanding how to properly subnet your network, you’ll improve efficiency, security, and scalability, all while optimizing performance. Whether you're designing a home network or managing an enterprise environment, this knowledge will make you an even more effective network engineer.
Next time you’re handed an IP address range and asked to split it up, you’ll do it with confidence, precision, and maybe even a little bit of swagger. So, what’s next on your network journey? Go out there and subnet like a pro!
Until next time, may your IP addresses always be properly configured, and your subnets perfectly divided.
Thanks,
Tor – Your trusted network engineering uplink
Comments