[Madalitso Cheyo]

Effective subnet allocation in IPv6 is about creating a logical, scalable, and easily manageable structure. Since address space is abundant, the focus is entirely on organization rather than conservation.

Allocate in Powers of Two. Always assign address blocks in powers of two (/49, /50, /51, etc.) rather than exact-fit allocations. This keeps the address plan aligned to bit boundaries, simplifies summarization, and makes future expansion cleaner without requiring renumbering.

Leave Gaps Between Allocations. Never assign blocks back-to-back. Leaving unallocated space between assignments allows sites, departments, or regions to grow without disrupting neighboring allocations. Address space is plentiful; use it generously.

Use a Top-Down Hierarchy. Structure allocations from the largest entity down to the smallest. A typical hierarchy looks like:

[Madalitso Cheyo]

IPv6 subnetting works on the same fundamental principle as IPv4; borrowing bits from the host portion to create smaller network segments, but the vast address space changes the approach entirely.

The Foundation: Always Start with /64. Every end-user subnet in IPv6 should be a /64, regardless of how many hosts it contains. This is not a recommendation but a requirement for SLAAC, EUI-64, and Neighbor Discovery to function correctly. Unlike IPv4, there is no need to size subnets to the number of hosts.

The Subnetting Space. A typical organization receives a /48 prefix, leaving 16 bits (bits 49–64) for subnetting. This allows for 65,536 /64 subnets. Subnetting simply means deciding how to assign those 16 bits hierarchically across your organization.

How to Subnet. To create subnets, bits are borrowed from the subnet field. For example, borrowing 4 bits from a /48 creates 16 possible /52 blocks. Each /52 can then be further divided into smaller blocks down to /64. The formula is always 2ⁿ, where n is the number of borrowed bits.

Point-to-Point Links. Router-to-router links are commonly assigned /127 prefixes (as per RFC 6164) instead of /64, since only two addresses are needed. /128 is used for loopback addresses, identifying a single device.

Key Subnetting Rules. Never subnet below /64 for end-user networks. Plan hierarchically by assigning larger blocks to regions or sites, then subdividing internally. Always leave room for growth by allocating in powers of two and leaving gaps between assignments.

[Madalitso Cheyo]

Understanding how much IPv6 address space your organization needs starts with recognizing that IPv6 planning is about structure and hierarchy, not conservation. The goal is to request enough space to accommodate current needs, future growth, and logical organization.

Standard Allocation for Enterprises. Most enterprises receive a /48 prefix from their ISP or RIR. This provides 16 bits of subnet space, yielding 65,536 subnets of /64 each. For the vast majority of organizations, a /48 is more than sufficient for current and future needs.

Breaking Down the /48. A typical enterprise can structure their /48 as follows:

First 48 bits → Global Routing Prefix (assigned by ISP/RIR)

Next 16 bits → Subnet ID (managed internally)

Last 64 bits → Interface ID (host addressing)

Estimating Your Subnet Requirements. When planning, count the number of distinct network segments needed, including user VLANs, server segments, DMZs, management networks, point-to-point links, loopbacks, guest networks, and branch offices. Each of these gets a /64 regardless of size.

Planning for Growth. A good rule is to allocate address blocks in powers of two and leave generous gaps between them. For example, if a branch office currently needs 10 subnets, allocate a /52 to that branch, giving it 16 subnets worth of space with room to grow without renumbering.

When a /48 Is Not Enough. Very large enterprises such as multinational corporations, universities, or cloud providers may request a /32 or larger directly from an RIR. This provides an entire block of /48s to distribute across divisions, campuses, or regions, enabling a truly hierarchical global addressing plan.

[Madalitso Cheyo]

A well-structured IPv6 address plan is critical for scalability, manageability, and efficient routing. Unlike IPv4, IPv6 provides an enormous address space, so the focus shifts from conservation to organization and clarity.

Start with your allocated prefix. Most organizations receive a /48 prefix from their ISP or Regional Internet Registry (RIR). This gives 16 bits for subnetting, allowing up to 65,536 subnets, each with a /64 prefix containing 18 quintillion host addresses.

Use a consistent subnet size. Always use /64 for end-user subnets regardless of how many hosts are needed. This ensures compatibility with SLAAC, EUI-64, and Neighbor Discovery Protocol. Avoid the IPv4 habit of sizing subnets to the number of hosts.

Plan a logical hierarchy. Divide your address space into structured tiers; for example, allocating specific ranges for data centers, branch offices, management networks, and DMZs. A clear hierarchy simplifies routing, troubleshooting, and future growth.

Reserve space for growth. Allocate address blocks generously and leave gaps between assignments. Since address space is abundant, there is no reason to assign blocks back-to-back, which would complicate future expansion.

Document everything. Maintain an IP Address Management (IPAM) system that records every assigned prefix, its purpose, location, and owner. Good documentation is the foundation of a manageable network.

Avoid embedding IPv4 addresses. While it may seem convenient to map IPv4 subnets into IPv6 (e.g., using the last octets of an IPv4 address as the subnet ID), this practice limits scalability and creates confusion as the network grows.

[Madalitso Cheyo]

Configuration on RouterOS is done through either the terminal or WinBox GUI. IPv6 is enabled per interface by adding an address under /ipv6 address add, specifying the address, prefix length, and interface. Unlike Cisco IOS, RouterOS does not require a global command to enable IPv6 routing; it is active as soon as an IPv6 address is assigned. A static default route is added under /ipv6 route add with the destination ::/0 and the next-hop gateway address. Link-local addresses are automatically generated on every IPv6-enabled interface but can be manually overridden if needed.

Verification uses RouterOS print commands. /ipv6 address print lists all assigned IPv6 addresses and their associated interfaces. /ipv6 route print displays the IPv6 routing table, confirming the default route and any other installed routes point to the correct next-hop. /ipv6 neighbor print shows the Neighbor Discovery table, mapping IPv6 addresses to MAC addresses similarly to ARP in IPv4. Connectivity is tested using the built-in /ping command with an IPv6 address specified, and link-local pings require the interface to be included.

Troubleshooting starts by confirming the interface is active and has a valid IPv6 address using /ipv6 address print. If hosts cannot reach external networks, /ipv6 route print is checked to ensure the default route exists and is active. Missing or incomplete Neighbor Discovery entries in /ipv6 neighbor print suggest a layer 2 connectivity problem. If traffic is being unexpectedly dropped, firewall rules under /ipv6 firewall filter print should be reviewed to ensure IPv6 traffic is permitted. For deeper diagnosis, /ipv6 firewall connection print tracks active IPv6 connections, and the torch tool under /tool torch can be used to monitor live IPv6 traffic on a specific interface.

[Madalitso Cheyo]

IPv6 is the modern replacement for IPv4. We need it because IPv4 addresses are nearly exhausted, and IPv6 provides enough addresses, simpler routing, better security, and scalability for the future of the internet.

[Madalitso Cheyo]

IPv4 has lasted because it was simple, adaptable, and extended by tricks like NAT and CIDR. But it’s not sustainable because its address space is too small for the modern, device-heavy internet.

[Madalitso Cheyo]

MLD in IPv6 stands for Multicast Listener Discovery. It’s essentially the IPv6 equivalent of IGMP (Internet Group Management Protocol) in IPv4. MLD helps IPv6 routers know which devices want which multicast traffic, making network communication more efficient.

[Madalitso Cheyo]

You cannot use IPv6 if your ISP doesn’t support it. But using tunneling services or VPNs can give you IPv6 connectivity without waiting for your ISP.