Skip to main content

IP in Practice: The Need for IPv6

 It is time for IPv6. Not just for our network infrastructure, but for this series. The IPv4 section has come to an end, and now it is time for a deep dive into IPv6. More than ever, it is time to consider systems that can handle heavier workloads, more devices, and fewer address limitations - AI agents, IoT devices, edge computing.

This post will examine why we need IPv6 and why it is an important network solution.  

Why do we need IPv6?

We need more space.

IPv6 literally increases the address space exponentially. The IPv6 address space is 2128 total addresses, 3.4 followed by 38 zeroes. Technology is no longer limited to servers, office computers, and mobile devices. Today's systems integrate AI infrastructure, edge computing, IoT devices, cloud networking, virtual machines, and more. Simply, more devices mean more space. 

We need more scalability.

As more devices connect to systems, administrators need to consider not only the number but the distribution. Systems and devices are now distributed over continents. Cloud systems need to provide resources to people and organizations. Many cloud providers offer IPv4 and IPv6 addressing, such as AWS EC2. 

We need more uniqueness.

In 2025, there are over 21.1 billion IoT devices alone in the entire world. Imagine giving each of those devices an IPv4 address. It is impossible. With IPv6, you have enough bits to fit several subnets of that number alone. 

Why is IPv6 an important network solution?

In an evolving technological field, we need a solution that meets demand and rising supply. IPv6 meets the task, even beyond the address space

1. IPv6 is efficient.

IPv6 has a larger address space, but an IPv6 packet is much more simplified compared to IPv4. In the next post, I will break down the IPv6 packet and how it compares with an IPv4 packet's fields. 

2. NAT is no longer necessary.

Network address translation existed to save the remaining public IPv4 address by translating private IP addresses. Since there are so many IP addresses that can be given within a IPv6 subnet, there are dedicated subnets that are globally routable. With IPv6, private addresses are no longer dependent on a private address space, like IPv4.

3. Simplified network management

IPv4 systems commonly rely on a DHCP server to get their address. If the DHCP server goes down, then devices won't be able to receive an IP address and not access resources or the Internet. However, an IPv6 system can get an IP address using DHCPv6 or offline using SLAAC. Stateless address auto-configuration allows devices to generate their own IP addresses. The SLAAC configuration process will be discussed in a future post. 

One thing about IPv6

Since IPv6 removes the need for a dedicated private subnets, like RFC1918, the question remains: How many systems can use IPv6? Unless your system incorporates tunneling or a dual stacking technique, IPv4 cannot communicate with IPv6 natively. In addition, is it needed in your infrastructure? On a public-facing basis, it resolves the addressing issue. Even internally, however, an IPv4 subnet may suffice. 

Moving on from the technical side, how about the operational side? Even if IPv4 and IPv6 could communicate with each other, implementing tunneling, dual stacking, and other techniques brings in complexity and added overhead. IPv4 works. As the adage goes, If it ain't broke, don't fix it. I'm not saying to fix it. I am saying adjust it. 

In the next section, we will discuss the structure of the IPv6 address and packet. 

Labels:

Comments

  1. AnonymousFebruary 26, 2026 at 9:31 AM

    Very good summary. In the meantime we have crossed 60% v6 penetration worldwide with some 3.3 billion users. So our call now is to move to v6-Only. Please visit the website of the IPv6 Forum: https://ipv6forum.org

    ReplyDelete

Post a Comment

Popular posts from this blog

Subnetting Tips

When I was first introduced to subnetting, it was difficult to understand the math and the process behind it. I watched videos but it did not click. I focused more on how to calculate it than on the reasoning behind it. Why do we subnet? I remember seeing forward slashes followed by numbers, classes, letters, network and broadcast addresses - important terms that was overshadowed by just trying to grasp why certain numbers were used.  Years later, I hear the word "subnetting" in one of my courses, and it reminded me of my struggles. Yet, I was excited. It was a time for redemption. Example after example, I started to get them right but also got to understand how to create a subnet with sufficient space for devices. Because of this, I have grown to love subnetting.  For me, it took time - a break that lasted about two years followed by a curriculum that focused on the topic for a few weeks. If you find yourself struggling with subnetting, do not worry. It takes time. If someth...
Post a Comment
Read more

How to Set Up a Cisco Router as a DHCP Server (Step-by-Step Guide)

Lab time! Want to build a DHCP server?  In this lab, I will show you how to build your own DHCP server on a router using Cisco Packet Tracer, as shown above. By the end of this post, you will be able to create your own DHCP server with a Cisco 2911 router, perhaps in a home lab setting, and prepare you to build your own on other hardware.  Why a Router?  A DHCP server is a centralized, automated service that assigns important network configuration details to devices on a network, such as IP addresses. Without it, we would have to create manual entries for our entire network, which can be time-consuming and lead to errors. Traditionally, there are dedicated servers to handle these functions. There are many ways to implement a DHCP server in your topology, including a dedicated physical server, a virtual machine, cloud-based gateways, and firewalls. However, there are specific benefits to using a router as your DHCP server: Reduced infrastructure: While havi...
Post a Comment
Read more

New Series: IP in Practice

I have done a few posts on subnetting and the inner workings of DHCP. I wanted to do a post on IPv6 and a hands-on demo on implementing DHCP on actual networking equipment. However, I missed a few parts that I would like to cover that would particularly help in understanding how IP works and why it is needed. Unlike the previous series, this will be a direct approach to a certain protocol: Internet Protocol (IP). I recently started my first series, covering important ports, protocols, and acronyms used in the networking field. However, I realized not only is it difficult to address the ones to mention, but for some letters it's hard to find. The intended structure was to have several per letter not just one. The idea seemed fun and engaging, however, doing over 20 posts alphabetically on acronyms, ports, and protocols lacks order and deviates from the direct approach I want this blog to have. For that reason, I am putting it on hold indefinitely. It was fun at first, but it was not...
Post a Comment
Read more