IPv6 Address Types
Every IPv6 address belongs to a type, and the leading bits tell you which. Cisco and the exam expect you to recognise a global unicast, a link-local, a unique local, and a multicast address on sight — and to know the handful of special groups that make IPv6 self-configuring.
The address-type map
Because an IPv6 address is enormous, the designers reserved large blocks for particular jobs and gave each block a distinctive leading-bit pattern. That prefix is how a router looks at the first few bits and instantly knows the address type without any configuration. The table below is the one you must be able to reproduce from memory.
| Type | Prefix | Purpose |
|---|---|---|
| Global unicast | 2000::/3 | Globally routable addresses on the public Internet. |
| Link-local | FE80::/10 | Automatic, non-routable addresses valid only on one link. |
| Unique local | FC00::/7 | Private addresses, the IPv6 analogue of RFC 1918. |
| Multicast | FF00::/8 | One-to-many delivery to a group. |
| Loopback | ::1/128 | The interface’s own address, like IPv4 127.0.0.1. |
| Unspecified | ::/128 | “No address yet”, used before a host is configured. |
2 or 3 are global unicast; FE80 is link-local; FC or FD is unique local; FF is multicast. When a question shows a hex address, classify it by the first hextet before reading anything else.Global unicast (2000::/3)
Global unicast addresses are the equivalents of public IPv4 addresses: they are globally unique and routable across the Internet. All of them fall in the block 2000::/3, whose first three bits are 001. That block spans from 2000:: up to 3FFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF — one eighth of the entire 128-bit space, about 2125 addresses.
A global unicast address is structured in three logical parts: the global routing prefix (typically the first 48 bits assigned to a site), the subnet ID (the next 16 bits, used to number LANs), and the interface identifier (the final 64 bits). The boundary is set by the prefix length the ISP gives you — usually /48 — and Lesson 15 shows how to carve it into /64 LANs.
2000::/3. Example: 2001:db8:acad:1::10/64.Link-local (FE80::/10)
Every IPv6-enabled interface automatically builds a link-local address the moment it comes up, even before any router has spoken to it. Link-local addresses live in FE80::/10, so they always begin with FE80 through FEBF. They are not routable: a router never forwards a packet whose source or destination is link-local past the local link.
Their importance is easy to underestimate. Link-local addresses carry almost all of IPv6’s control traffic: neighbour discovery, router solicitation and advertisement, and the next-hop field of IPv6 routes. When a router sends you a route to a remote network, the “next hop” is the neighbour’s link-local address, not its global one. That is why an interface with only a link-local address can still participate fully in routing (Lesson 17).
- Always start with
FE80; the last 64 bits are the interface ID. - Mandatory on every IPv6 interface that is up.
- Each interface generates its own; a router has one per active interface.
- Use the
%zone index in CLI/testing to say which link, e.g.FE80::1%GigabitEthernet0/0.
FE80:: address on both. The interface is what disambiguates them, which is why you must name the interface (or zone index) when pinging a link-local address.Unique local (FC00::/7)
Unique local addresses (ULA) sit in FC00::/7 and are the direct answer to RFC 1918 private IPv4 space. They are private, not routable on the public Internet, and intended for internal use. The block is split by the first bit after the 1111 110 pattern: addresses beginning FD are locally assigned and are the ones in actual use; the FC half was reserved for a central authority but has never been allocated.
A ULA typically has a 40-bit random global ID to make collisions between organisations unlikely, followed by a 16-bit subnet ID and a 64-bit interface ID. In practice organisations often use FD00::/8 with a random global ID, giving a result such as FD12:3456:789A:1::/64. ULAs are useful for a network that must not depend on an ISP prefix (for example, internal-only services) and is not expected to reach the Internet.
Multicast (FF00::/8)
IPv6 has no broadcast. Where IPv4 shouted to everyone with a broadcast, IPv6 uses multicast: one packet addressed to a group, delivered only to the members that joined it. All multicast addresses begin FF and fall in FF00::/8. The second hextet carries flags and a scope field; the most common scope is 2, meaning link-local.
| Multicast address | Group | Used by |
|---|---|---|
FF02::1 | All-nodes | Every IPv6 host on the link; the closest thing to a broadcast. |
FF02::2 | All-routers | Every IPv6 router on the link; hosts send solicitations here. |
FF02::1:FFxx:xxxx | Solicited-node | Built from the last 24 bits of a unicast address; used by neighbour discovery and DAD (Lesson 16). |
FF02::5 | All OSPFv3 routers | OSPFv3 Hello and update traffic. |
FF02::6 | OSPFv3 DRs/BDRs | OSPFv3 messages destined to the designated router. |
FF02::1:2 | All DHCPv6 servers/relays | DHCPv6 client requests (Lesson 16). |
The solicited-node multicast address deserves special attention because it replaces ARP. When a host needs the MAC address of a neighbour, or wants to check whether its own address is duplicated, it sends to the solicited-node group rather than to everyone. The address is formed by taking the prefix FF02::1:FF00:0/104 and appending the last 24 bits of the target unicast address. If a host’s address ends in ...:8329, its solicited-node group is FF02::1:FF00:8329 — only the low 24 bits matter, so collisions are rare but possible.
FF02::1:FF and append the last six hex digits of its unicast address. Remember the three link groups: FF02::1 all nodes, FF02::2 all routers, FF02::1:FFxx:xxxx solicited-node.Anycast
IPv6 defines three delivery models. Unicast is one-to-one. Multicast is one-to-many (the many who joined the group). Anycast is one-to-nearest-of-many: the same address is configured on multiple devices, and a packet sent to it is delivered to whichever instance the routing protocol considers closest. Anycast is defined by its behaviour, not by a distinct address range — an anycast address is simply a unicast address assigned to more than one node.
Anycast is how services like DNS roots and content delivery networks place one address in many data centres; the Internet’s routing then steers each user to the nearest copy. Because only one member answers, anycast needs an underlying unicast routing protocol (OSPF, BGP) and no new address block.
Loopback and unspecified
Two all-purpose special addresses round out the set.
- Loopback —
::1/128. A host uses it to test its own IPv6 stack, exactly as IPv4 uses 127.0.0.1. It is never assigned to a physical interface and is never forwarded. - Unspecified —
::(all zeros). This means “no address yet”. A host with no configured address uses it as the source when it first talks to a DHCPv6 server or asks a router for a prefix. It is valid only as a source, never as a destination.
Do not confuse the two. ::1 is a usable loopback address; :: is a placeholder that signals an unconfigured interface.
EUI-64 interface identifiers
The right 64 bits of an address identify the interface. They can be set manually, generated randomly (the default for modern operating systems, for privacy), or derived from the interface’s 48-bit MAC address using the EUI-64 process. Cisco IOS still offers the EUI-64 form, and the exam expects you to know how it is built.
The steps are:
- Take the 48-bit MAC address, e.g.
001A:2B3C:4D5E. - Split it in half:
001A 2Band3C4D 5E. - Insert
FFFEbetween the halves:001A:2BFF:FE3C:4D5E. - Flip the 7th bit (the universal/local bit) of the first byte:
00becomes02, so the interface ID is021A:2BFF:FE3C:4D5E.
Appending that to a prefix gives a full address such as 2001:db8:acad:1:021a:2bff:fe3c:4d5e. The bit flip marks the address as “locally administered” in EUI-64 terms. Although it is elegant, EUI-64 exposes the hardware MAC and makes a device trackable, so privacy addressing (temporary random interface IDs) is the default on Windows, macOS, Android, and iOS today.
Review
Check what you have learned with these review questions.
Sources & references
- Hinden, R. & Deering, S. RFC 4291: IP Version 6 Addressing Architecture (2006) — unicast, multicast, anycast and special addresses. rfc-editor.org/rfc/rfc4291.
- Hinden, R. & Haberman, B. RFC 4193: Unique Local IPv6 Unicast Addresses (2005) — the FC00::/7 block. rfc-editor.org/rfc/rfc4193.
- Hinden, R. & Deering, S. RFC 2373: IP Version 6 Addressing Architecture (1998) — original EUI-64 and solicited-node definitions. rfc-editor.org/rfc/rfc2373.
- IANA. IPv6 Multicast Address Space Registry. iana.org.
- Cisco. CCNA (200-301) Exam Topics, Network Fundamentals — IPv6 address types. cisco.com.
Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.