IPv6 Subnetting and Prefixes
IPv6 subnetting is not the bit-pushing arithmetic of IPv4. Because a /64 gives a LAN more addresses than any site can use, the job becomes prefix planning: split the /48 you were given into tidy /64s and decide which one each VLAN gets.
The structure of a global unicast address
A global unicast address is not one undifferentiated number. The IPv6 architecture gives the first 64 bits a job and the last 64 bits another job, and it further divides the first 64 for routing and subnetting. For the common case of a site that receives a /48, the address breaks down like this.
| Field | Bits | Meaning |
|---|---|---|
| Global routing prefix | 48 | Assigned to the organisation by its ISP; globally unique and routed on the Internet. |
| Subnet ID | 16 (bits 49–64) | Chosen by the site to number its own LANs. 16 bits = 65,536 subnets. |
| Interface ID | 64 (bits 65–128) | Identifies the interface on the subnet; often SLAAC- or EUI-64-derived. |
The critical difference from IPv4 is the scale. The subnet ID alone is 16 bits, so one /48 yields 216 = 65,536 /64 subnets. And each /64 contains 264 addresses — about 18 quintillion. You will never run out, so the design goal shifts from “conserve addresses” to “organise addresses so a human can read them”.
2001:db8:acad::/48, the first LAN is 2001:db8:acad:0::/64 and the VLAN 10 LAN might be 2001:db8:acad:a::/64.Common prefix lengths: /32, /48, /64
You will see the same three prefix lengths again and again, each belonging to a different layer of the allocation hierarchy. Learn the role each plays.
| Prefix | Field | Assigned to / used for |
|---|---|---|
/32 | Global routing prefix | Allocated by a regional registry (RIR) to a large ISP or organisation. Example: 2001:db8::/32. |
/48 | Global routing prefix | Allocated by an ISP to one customer site. Example: 2001:db8:acad::/48. |
/64 | Global routing prefix + subnet ID | The standard LAN prefix, one per subnet; required by SLAAC. |
/128 | Full address | A single interface address (host route), like IPv4 /32. |
The chain is easy to remember as a funnel: the registry gives a /32 to the ISP, the ISP gives a /48 to the site, and the site splits its /48 into /64 LANs. Nothing smaller than /64 is normally assigned to a link, precisely because SLAAC mandates it.
Subnetting a /48 into /64s
The arithmetic is refreshingly simple. A /48 to a /64 leaves the 16-bit subnet ID as the only field that changes. To step from one subnet to the next, increment the fourth hextet (the first hextet after the 48-bit prefix). Because a hextet is 16 bits, the fourth hextet is the subnet ID.
So for the site prefix 2001:db8:acad::/48:
- Subnet 0:
2001:db8:acad:0::/64 - Subnet 1:
2001:db8:acad:1::/64 - Subnet 10 (hex
a):2001:db8:acad:a::/64 - Last subnet:
2001:db8:acad:ffff::/64
The interface ID within each subnet is not zero-padded to a fixed value; it is left for SLAAC or the administrator. Writing ::/64 simply means the interface ID is all zeros, which is useful as a subnet label.
A worked hierarchy
Put the whole funnel together. A regional registry allocates 2001:db8::/32 to an ISP. The ISP assigns 2001:db8:acad::/48 to a campus. The campus plans its VLANs.
| VLAN | Subnet ID | LAN prefix | Gateway idea |
|---|---|---|---|
| VLAN 10 (users) | 000a | 2001:db8:acad:a::/64 | Router uses ::1 on the LAN. |
| VLAN 20 (voice) | 0014 | 2001:db8:acad:14::/64 | SLAAC hosts learn it automatically. |
| VLAN 30 (servers) | 001e | 2001:db8:acad:1e::/64 | Servers often get DHCPv6 or static addresses. |
| WAN / transit | 00ff | 2001:db8:acad:ff::/64 | Point-to-point link; /64 is still used. |
Notice that each VLAN is a /64 and the subnet ID is chosen to mirror the VLAN number. This makes the prefix self-documenting: anyone seeing 2001:db8:acad:a::/64 knows it is VLAN 10 at the acad site. Even point-to-point links get a /64, because reserving a smaller block buys nothing and would break SLAAC.
/127 on point-to-point links to save address space and avoid certain neighbour-discovery issues. The CCNA exam and most designs still use /64 everywhere; if a question insists on the standard LAN size, answer /64.SLAAC and the 64-bit interface ID
SLAAC (Lesson 16) lets a host configure itself with no server. The host receives a /64 prefix in a Router Advertisement and appends its own 64-bit interface ID. For that to work, the LAN prefix must be exactly /64; a host cannot infer a different boundary. This is the practical reason /64 is the universal LAN size, and why network designers do not invent odd prefix lengths for LANs.
The interface ID may be built in one of three ways:
- EUI-64 — derived from the MAC address (Lesson 14). Predictable but exposes hardware.
- Random (privacy) — the default on modern operating systems; the ID changes periodically.
- Stable / DHCPv6 — assigned by an administrator or a DHCPv6 server for servers and printers that need a fixed address.
For the exam, the takeaway is the coupling: RA gives the first 64 bits, the host supplies the last 64 bits. If a question presents a LAN with a non-/64 prefix and asks whether SLAAC will work, the answer is no.
Address planning
Because the space is effectively unlimited, good IPv6 planning is about readability and summarisation, not conservation. A few rules of thumb:
- Use a single /48 per site. Keep all of a site’s prefixes under one global routing prefix so the site can be advertised to the Internet with one summary route.
- Mirror the VLAN number in the subnet ID so an operator can decode a prefix at a glance (VLAN 10 →
:a::/64). - Leave blocks for future growth. Reserve ranges for a new building or a new class of device rather than filling low subnet IDs first.
- Document the plan. Unlike IPv4 where you could almost count on your fingers, IPv6 numbering must be written down.
- Keep control-plane prefixes simple. Use
::1for router LAN interfaces,::2for the next device, and reserve a small range for infrastructure.
Review
Check what you have learned with these review questions.
Sources & references
- Hinden, R. & Deering, S. RFC 4291: IP Version 6 Addressing Architecture (2006) — the /48 site and /64 subnet structure. rfc-editor.org/rfc/rfc4291.
- Narten, T. et al. RFC 4862: IPv6 Stateless Address Autoconfiguration (2007) — /64 requirement for SLAAC. rfc-editor.org/rfc/rfc4862.
- IANA. IPv6 Global Unicast Address Assignments. iana.org.
- Hinden, R. & Haberman, B. RFC 4193: Unique Local IPv6 Unicast Addresses (2005). rfc-editor.org/rfc/rfc4193.
- Cisco. CCNA (200-301) Exam Topics, Network Fundamentals — configure and verify IPv6 addressing and prefix. cisco.com.
Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.