{"id":169051,"date":"2026-06-18T11:39:47","date_gmt":"2026-06-18T08:39:47","guid":{"rendered":"https:\/\/computingforgeeks.com\/?p=169051"},"modified":"2026-06-18T11:39:47","modified_gmt":"2026-06-18T08:39:47","slug":"ipv6-addressing-explained","status":"publish","type":"post","link":"https:\/\/computingforgeeks.com\/ipv6-addressing-explained\/","title":{"rendered":"IPv6 Addressing Explained: Address Types and EUI-64"},"content":{"rendered":"\n

IPv6 exists because the 32-bit IPv4 address space ran out: roughly 4.3 billion addresses was never going to cover the modern internet. IPv6 uses 128-bit addresses, which is an almost unimaginably larger pool, but the size is not the part that trips people up. What trips people up is the five address types that all look similar and the EUI-64 math that turns a MAC address into an interface ID. This guide covers the address format, how to identify any address by type, what each type is for, the EUI-64 process worked out against real router output, and how to configure IPv6 on a Cisco router.<\/p>\n\n\n\n

The behavior and command output described here were checked on a Cisco IOS router (a GNS3 c7200) in June 2026. It assumes you are comfortable with IPv4 addressing<\/a> and prefix notation; if not, the subnetting primer<\/a> covers the \/n prefix idea that carries straight over to IPv6.<\/p>\n\n\n\n

What an IPv6 address looks like<\/h2>\n\n\n\n

An IPv6 address is 128 bits, written as eight groups of four hexadecimal digits separated by colons. Written in full, an address is long, so two abbreviation rules shorten it. First, drop the leading zeros in any group. Second, replace the single longest run of consecutive all-zero groups with a double colon (::<\/code>), which may appear only once in an address. The key insight is that ::<\/code> can appear once because a parser fills it back out by counting the groups on either side; allow it twice and the length becomes ambiguous.<\/p>\n\n\n\n

Here is the same address written long and short:<\/p>\n\n\n\n

Form<\/th>Address<\/th><\/tr><\/thead>
Full<\/td>2001:0DB8:0000:0001:0000:0000:0000:0001<\/td><\/tr>
Leading zeros dropped<\/td>2001:DB8:0:1:0:0:0:1<\/td><\/tr>
Longest zero run as ::<\/td>2001:DB8:0:1::1<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Prefix length works exactly as in IPv4: a \/n<\/code> after the address marks how many leading bits are the network portion. For LAN subnets that value is almost always \/64<\/code>, which splits the address into a 64-bit network half and a 64-bit host (interface) half.<\/p>\n\n\n\n

How to identify an IPv6 address by its first digits<\/h2>\n\n\n\n

The type of an IPv6 address is decided by its first digit or two, so identification is a lookup, not a calculation. This is the table worth keeping in your head:<\/p>\n\n\n\n

First digits<\/th>Address type<\/th>Routability<\/th>Notes<\/th><\/tr><\/thead>
2 or 3<\/td>Global unicast<\/td>Internet-routable<\/td>Assigned by an ISP or RIR (2000::\/3)<\/td><\/tr>
FD<\/td>Unique local<\/td>Site only, not on the internet<\/td>The RFC 1918 of IPv6<\/td><\/tr>
FE80<\/td>Link-local<\/td>One link only, never forwarded<\/td>Auto-generated on every interface<\/td><\/tr>
FF<\/td>Multicast<\/td>Scope-dependent<\/td>Replaces broadcast; no unicast use<\/td><\/tr>
FC<\/td>Unique local (reserved)<\/td>None today<\/td>Officially reserved, not deployed<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Anycast is the exception: it has no prefix of its own. An anycast address looks identical to a global unicast or unique local address, and the only difference is administrative, covered below.<\/p>\n\n\n\n

Global unicast addresses<\/h2>\n\n\n\n

A global unicast address (GUA) is the IPv6 equivalent of a public IPv4 address: globally unique and routable on the internet. It starts with a 2 or 3 (the 2000::\/3 block). What’s actually happening inside a GUA is a three-part split. The first 48 bits are the Global Routing Prefix your ISP or regional registry assigns. The next 16 bits are a Subnet ID you control, enough for 65,536 subnets. The last 64 bits are the Interface ID, the host part.<\/p>\n\n\n\n

\"IPv6<\/figure>\n\n\n\n

The 64-bit boundary matters because it is where the host part begins, and it is the line that EUI-64 and stateless autoconfiguration both work against. A site that receives a \/48 from its ISP has 16 subnet bits to carve \/64 networks from, which is the standard enterprise layout. The carving is the same binary exercise as variable-length subnetting<\/a> in IPv4, only with so many bits that you rarely subnet below \/64.<\/p>\n\n\n\n

Unique local addresses<\/h2>\n\n\n\n

Unique local addresses (ULAs) are the RFC 1918 of IPv6: usable inside a site, never routed on the public internet. In practice they always begin with FD<\/code>. The standard reserves the wider FC00::\/7 block, but RFC 4193 requires a bit that forces the second hex digit to D, so a real ULA is always FD<\/code>; FC<\/code> is reserved and unused. After the FD<\/code> comes a 40-bit Global ID that you are meant to generate randomly, which is what keeps two organizations from colliding when they merge networks that both use internal IPv6. A ULA looks like FD00:1234:5678:1::1\/64<\/code>, and you configure it exactly like a GUA.<\/p>\n\n\n\n

Link-local addresses and the EUI-64 process<\/h2>\n\n\n\n

Every IPv6-enabled interface gets a link-local address automatically, with no configuration, the moment IPv6 is active on it. Link-local addresses always begin FE80<\/code> and are never forwarded past the local link. They are not a curiosity: the mechanism that discovers a neighbor’s MAC (NDP, the IPv6 replacement for ARP) runs over link-local, routing protocols form neighbor adjacencies over link-local, and the next hop in an IPv6 routing table<\/a> is a link-local address, not a global one. That last point surprises people the first time they read show ipv6 route<\/code>: the next hop they expected to be a global address is an FE80<\/code> one, because link-local addresses never change even when the global prefix does.<\/p>\n\n\n\n

Cisco IOS builds the interface ID for that link-local address with modified EUI-64, a four-step process that turns a 48-bit MAC into a 64-bit interface ID. Worked out against the lab router’s MAC of 0201.ABCD.0001<\/code>:<\/p>\n\n\n\n

Step<\/th>Action<\/th>Result<\/th><\/tr><\/thead>
1<\/td>Start with the 48-bit MAC (12 hex digits)<\/td>0201.ABCD.0001<\/td><\/tr>
2<\/td>Split it into two 24-bit halves<\/td>0201AB and CD0001<\/td><\/tr>
3<\/td>Insert FFFE between the halves<\/td>0201:ABFF:FECD:0001<\/td><\/tr>
4<\/td>Flip the 7th bit of the first byte (02 becomes 00)<\/td>0001:ABFF:FECD:0001<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The interface ID is 0001:ABFF:FECD:0001<\/code>, so the link-local address is FE80::1:ABFF:FECD:1<\/code>. The two giveaways that an address came from EUI-64 are the FF:FE<\/code> sitting in the middle and the flipped 7th bit. The router output confirms the math exactly, on both the link-local and the EUI-64 global address:<\/p>\n\n\n\n

\"Cisco<\/figure>\n\n\n\n

Multicast addresses<\/h2>\n\n\n\n

IPv6 has no broadcast. Multicast does that job, and every multicast address begins with FF<\/code>. The fourth hex digit encodes scope, which is how far the packet travels: FF02<\/code> is link-local scope (stays on the link), while FF0E<\/code> is global. A handful of link-local multicast groups appear constantly and are worth memorizing.<\/p>\n\n\n\n

Address<\/th>Group<\/th><\/tr><\/thead>
FF02::1<\/td>All nodes on the link<\/td><\/tr>
FF02::2<\/td>All routers on the link<\/td><\/tr>
FF02::5<\/td>All OSPFv3 routers<\/td><\/tr>
FF02::6<\/td>All OSPFv3 designated routers<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

These are not theoretical. The show ipv6 interface<\/code> capture above lists FF02::1<\/code> and FF02::2<\/code> under “Joined group address(es)”, alongside a solicited-node address (FF02::1:FFCD:1<\/code>) that NDP derives from the interface’s own address to do efficient neighbor discovery.<\/p>\n\n\n\n

Anycast addresses<\/h2>\n\n\n\n

An anycast address is one address assigned to several interfaces, usually on several routers. The network delivers a packet sent to that address to whichever holder is topologically nearest. There is no special prefix; an anycast address is drawn from the global unicast or unique local range and configured with an anycast<\/code> keyword so the device knows not to treat duplicates as a conflict. For CCNA the requirement is the concept, not deep configuration: same address, nearest node answers.<\/p>\n\n\n\n

Configuring IPv6 on a Cisco router<\/h2>\n\n\n\n

The one command people forget is the first one. IPv6 routing is off by default on a Cisco router, the opposite of IPv4. A router with addresses configured still drops any IPv6 packet not destined to itself until you enable routing globally:<\/p>\n\n\n\n

enable\nconfigure terminal\nipv6 unicast-routing\ninterface GigabitEthernet0\/0\nipv6 address 2001:DB8:CAFE:2::\/64 eui-64\nno shutdown\nend<\/code><\/pre>\n\n\n\n
The eui-64<\/code> keyword tells IOS to build the interface ID from the MAC, as worked out above. To set the whole address by hand instead, give the full address and prefix: ipv6 address 2001:DB8:CAFE:1::1\/64<\/code>. Verify both forms with show ipv6 interface brief<\/code>, which lists each interface with its automatic link-local address and its configured global address:<\/p>\n\n\n\n
\"Cisco<\/figure>\n\n\n\n
Each interface shows two addresses: the FE80<\/code> link-local that IOS generated on its own, and the global address you configured. That pairing, one automatic link-local and one routable global address per interface, is the normal IPv6 state, and it is the same workflow as the rest of the base device configuration<\/a>.<\/p>\n\n\n\n
Enabling routing also populates the routing table. Running show ipv6 route connected<\/code> on the lab router lists each configured \/64 as a directly connected route, the 2001:DB8:CAFE:1::\/64<\/code> and 2001:DB8:CAFE:2::\/64<\/code> prefixes that the router can now forward between. Without ipv6 unicast-routing<\/code>, those addresses still exist on the interfaces, but the router refuses to forward anything between them, which is the gotcha worth burning into memory.<\/p>\n\n\n\n
Practice IPv6 addressing<\/h2>\n\n\n\n
Drill the address types, the first-digit identifiers, and the EUI-64 steps with the flashcards, then test yourself on the quiz. The deck is a downloadable Anki package for spaced repetition.<\/p>\n\n\n
Loading flashcards...<\/div><\/div>\n\n\n\n
Now check what stuck:<\/p>\n\n\n
Loading quiz...<\/div><\/div>\n\n\n\n
Common IPv6 addressing misconceptions<\/h2>\n\n\n\n
Four ideas that carry over wrongly from IPv4 or from a quick skim of the address types.<\/p>\n\n\n\n
Link-local addresses are not throwaway.<\/strong> An FE80<\/code> address looks like noise, but it is what neighbor discovery, routing adjacencies, and routing-table next hops actually use. You never configure it, and you never ignore it either.<\/p>\n\n\n\n
The private prefix is FD, not FC.<\/strong> The standard reserves FC00::\/7, so it is tempting to write a private address starting with FC. Real unique local addresses always start with FD; FC is reserved and not in use.<\/p>\n\n\n\n
IPv6 does not need NAT to function.<\/strong> Unique local addresses give you private addressing, but the design intent is that every device can hold a real global address. NAT was an IPv4 workaround for scarcity, and IPv6 has no scarcity to work around.<\/p>\n\n\n\n
The double colon is a one-time tool.<\/strong> ::<\/code> compresses one run of zero groups per address. Using it twice makes the address ambiguous, so a parser rejects it. When two zero runs are equal length, compress the first. Get the address format and the five type prefixes solid, and the rest of IPv6 on the CCNA reads as routing and services layered on top of these same addresses. The CCNA 200-301 roadmap<\/a> shows what comes next.<\/p>\n","protected":false},"excerpt":{"rendered":"
IPv6 exists because the 32-bit IPv4 address space ran out: roughly 4.3 billion addresses was never going to cover the modern internet. IPv6 uses 128-bit addresses, which is an almost unimaginably larger pool, but the size is not the part that trips people up. What trips people up is the five address types that all … Read more<\/a><\/p>\n","protected":false},"author":3,"featured_media":169050,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[55],"tags":[524,525],"cfg_series":[39888],"class_list":["post-169051","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-networking","tag-ccna","tag-cisco","cfg_series-ccna-200-301"],"_links":{"self":[{"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/posts\/169051","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/comments?post=169051"}],"version-history":[{"count":2,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/posts\/169051\/revisions"}],"predecessor-version":[{"id":169057,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/posts\/169051\/revisions\/169057"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/media\/169050"}],"wp:attachment":[{"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/media?parent=169051"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/categories?post=169051"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/tags?post=169051"},{"taxonomy":"cfg_series","embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/cfg_series?post=169051"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}