VMware ESXi and vSphere Cluster Management

IPv6 Link-Local Addresses: Scope, Format, Uses, and Cisco IOS Configuration

Learn how IPv6 link-local addresses work, including FE80::/10, scope, automatic assignment, NDP, routing next hops, default gateways, and Cisco IOS commands.

An IPv6 link-local address is an IPv6 unicast address valid only on one directly connected Layer 2 network segment, also called a local link. Every IPv6-enabled interface needs a link-local address for local IPv6 operations, even when the interface also has a global unicast or unique local address.

Link-local addresses support communication between neighboring devices. They are not replacements for globally routable addresses when traffic must cross routers. For example, a host can use its router's link-local address as its IPv6 default gateway, but it cannot use that link-local address as a destination across several routed networks.

What Is a Local Link?

A local link is one directly connected Layer 2 segment or IPv6 subnet shared by neighboring interfaces. An Ethernet LAN is a common example. Devices on that LAN can communicate directly without an IPv6 router forwarding the packet to another link.

The scope of a link-local address is therefore one link. A packet addressed to a link-local destination must remain on the link where it is used. IPv6 routers do not forward a packet with a link-local destination onto another interface.

Link-Local Versus Other IPv6 Address Scopes

Why IPv6 Interfaces Need Link-Local Addresses

When IPv6 is enabled on an interface, the interface normally creates a link-local address automatically. This address gives the interface an identity for communication with directly connected IPv6 neighbors before a global address, DHCPv6 information, or other configuration is available.

IPv6 control-plane functions depend on this local identity. Neighbor Discovery Protocol (NDP) uses link-local communication to discover neighbors, resolve a neighbor's Layer 2 address, discover routers, and maintain neighbor reachability information.

Link-local addresses also allow a host to learn and use a router's local next hop. A router advertisement commonly tells a host that the router's link-local address is the default gateway for that LAN.

The FE80::/10 Prefix

FE80::/10 is the IPv6 prefix block reserved for link-local unicast addresses. The /10 means that the first 10 bits identify the allocation. In hexadecimal, the allocated range begins at FE80 and extends through FEBF in the first 16-bit block.

People often refer to link-local addresses as having the “FE80 prefix” because valid examples commonly display as FE80:: followed by additional fields. Strictly, however, FE80::/10 is broader than only addresses whose first 16 bits are exactly FE80. The important recognition rule is that a link-local address belongs to the FE80::/10 block.

Conceptual Address Structure

A standard link-local address can be understood as three conceptual areas:

• Link-local prefix area: the first 10 bits, represented by FE80::/10.
• Reserved portion: the next 54 bits are reserved and normally set to zero in the standard structure.
• Interface identifier: the final 64 bits identify the interface within the relevant link-local prefix context.

In the usual representation, this structure is commonly shown as a 64-bit prefix followed by a 64-bit interface identifier. The interface identifier may be generated automatically, randomly, by a stable algorithm, or from a MAC address using EUI-64, depending on the device and configuration.

IPv6 addresses use eight groups of four hexadecimal digits. Leading zeroes in a group may be removed, and one consecutive run of all-zero groups may be replaced with ::.

Expanded form:   FE80:0000:0000:0000:021A:2BFF:FE3C:4D5E
Compressed form: FE80::21A:2BFF:FE3C:4D5E

Both examples represent the same link-local address. The compressed form is the form most often seen in command output.

How Link-Local Addresses Are Assigned

Automatic Assignment

An IPv6 host or router interface normally generates a link-local address as soon as IPv6 is enabled. The device selects the interface identifier using its operating system's address-generation method. That method does not have to be EUI-64; many modern systems use stable or privacy-oriented algorithms instead.

Automatic assignment makes basic IPv6 neighbor communication possible without manually assigning an address to every interface. A generated link-local address should still be verified when documenting a network or troubleshooting a specific neighbor.

Manual Assignment

An administrator can assign a chosen link-local address. Predictable addresses such as FE80::1 on a router LAN interface can make diagrams, routing tables, configuration reviews, and troubleshooting easier.

A manually assigned link-local address must be unique on its particular local link. The same value may be used on an interface attached to a different link, because link-local scope prevents those two uses from being part of one address space for forwarding purposes.

Operational Uses

Neighbor Discovery Protocol

NDP is a collection of IPv6 control-plane functions. It uses local-link communication for tasks such as discovering neighboring devices, resolving IPv6 neighbors to Layer 2 addresses, learning router information, and checking whether a neighbor remains reachable.

Because these tasks concern directly connected neighbors, link-local addresses are a natural source and destination for much of this traffic.

Routing Protocol Next Hops

A next hop is the neighboring router or address to which a packet is sent for its next step toward a destination. IPv6 routing protocols can form router-to-router adjacencies and install routes using link-local addresses as next hops.

This does not mean the advertised destination network is link-local. The route may lead to a global or unique local network, while the immediate neighboring router is identified by its link-local address. The link-local next hop works because that neighbor is directly connected to the router installing the route.

Control-Plane Traffic Versus Application Traffic

Link-local addressing is especially important for control-plane functions such as NDP and routing protocols. Typical application traffic between endpoints generally uses global unicast or unique local addresses when it must travel beyond the local link.

Using Link-Local Addresses as Default Gateways

A host on an IPv6 LAN commonly uses the router interface's link-local address as its default gateway. For example, a router could use FE80::1 on a LAN interface, and hosts on that same LAN could select FE80::1 as the next hop for destinations outside the local subnet.

The gateway remains local to the host's LAN. The router receives the packet, examines its routed destination, and then forwards it using an appropriate outgoing interface. The host is not attempting to route a packet to FE80::1 through another router.

Router advertisements can provide default-router information automatically. A static host configuration can also specify a gateway, but the address must be valid on the host's local link.

Why an Interface or Zone May Be Required

The same link-local value can exist on multiple interfaces of one router or on devices attached to different links. For example, a router might use FE80::1 on both GigabitEthernet0/0 and GigabitEthernet0/1. This is valid because each occurrence belongs to a different link.

When an administrator sends traffic to a link-local destination, the destination address alone may not identify which link to use. The operating system or network command may therefore require a source interface or an interface zone. This additional information supplies the missing scope context.

ping ipv6 FE80::2 source GigabitEthernet0/0

On systems that use zone identifiers in textual addresses, the interface may appear as part of the address notation, such as an address followed by a zone name or number. The exact syntax varies by operating system. The principle is the same: identify the local interface through which the link-local destination should be reached.

Cisco IOS Configuration

On Cisco IOS, IPv6 forwarding is enabled globally with ipv6 unicast-routing. IPv6 processing can then be enabled on an interface with ipv6 enable. The exact interface name varies by router model and platform.

ipv6 unicast-routing
!
interface GigabitEthernet0/0
 ipv6 enable
 ipv6 address FE80::1 link-local

The ipv6 address FE80::1 link-local command manually assigns FE80::1 as the interface's link-local address. The link-local keyword tells IOS how to interpret the address. Choose an address that does not duplicate another link-local address on the same segment.

Verifying the Interface

Use the following commands to verify the interface state and IPv6 addresses:

show ipv6 interface brief
show ipv6 interface GigabitEthernet0/0

Look for an operationally active interface and a link-local address in the FE80::/10 range. The detailed interface command can also help confirm whether IPv6 is enabled and whether the address was configured manually or generated automatically.

Testing a Link-Local Neighbor

When testing a link-local neighbor from a Cisco router, specify the source interface:

ping ipv6 FE80::2 source GigabitEthernet0/0

The source interface tells IOS which local link should be used. Without that context, a link-local destination can be ambiguous.

Link-Local Address Characteristics

Troubleshooting Link-Local Connectivity

Link-Local Ping Fails

• Confirm that both interfaces are on the same Layer 2 link and are operationally up.
• Verify that IPv6 is enabled on both interfaces.
• Specify the correct source or outgoing interface when testing a link-local destination.
• Check for duplicate link-local addresses on the same segment.
• Verify that the neighbor's interface has the address currently shown in its IPv6 interface output.

An Attempt Is Made to Route to a Link-Local Address

A link-local destination cannot be reached through another router. The destination is constrained to the originating link. Use a global unicast or unique local address when communication must cross a routed boundary.

A Host Cannot Reach Its IPv6 Default Gateway

• Verify that the host and router interface share the same local link.
• Confirm that the configured gateway is the router address valid on that link.
• Check router advertisements or the host's static IPv6 configuration.
• Verify that NDP can discover and resolve the router on the LAN.
• Check that the router interface is up and has the expected link-local address.

A Manual Address Causes Neighbor Problems

• Search for a duplicate link-local address on the same subnet.
• Confirm that the Cisco IOS command includes the link-local qualifier.
• Review show ipv6 interface output after making the change.
• Make sure a test command uses the correct interface when the same address exists on another link.

Exam-Relevant Summary

• IPv6 link-local addresses identify interfaces only on their directly attached local link.
• The reserved range is FE80::/10; the commonly seen FE80 prefix is a shorthand recognition pattern, not the full explanation of the /10 boundary.
• IPv6 routers do not forward packets whose destination is link-local.
• An IPv6-enabled interface normally creates a link-local address automatically.
• Link-local addresses are used heavily by NDP and can serve as IPv6 routing-protocol next hops.
• A host commonly uses the router's link-local address as its IPv6 default gateway.
• The same link-local address can be reused on different links, but a source interface or zone may be required to identify the intended link.
• Manually configured addresses must be unique on their local link.

For related study, see IPv6 Link-Local Addresses as the reference lesson for this topic.