VMware ESXi and vSphere Cluster Management

IPv6 Address Types: Unicast, Multicast, Anycast, and Address Scope

Learn IPv6 unicast, multicast, anycast, global, link-local, unique local, loopback, and unspecified addresses, including prefixes, scopes, routing, and CCNA configuration.

IPv6 uses several address types because different communication tasks need different delivery behavior and reachability boundaries. The three top-level delivery types are unicast, multicast, and anycast.

An IPv6 address is assigned to an interface. An interface is a network connection on a host or router, such as an Ethernet port, wireless adapter, or virtual interface. A single interface can have multiple IPv6 addresses, including a link-local address and one or more global or unique local addresses.

IPv6 Delivery Models

IPv4 also has broadcast, which sends traffic to all hosts in a broadcast domain. IPv6 does not use broadcast addresses. IPv6 replaces common broadcast-dependent functions with multicast groups. Anycast can provide access to a nearby service instance, but it is not a one-for-one replacement for broadcast: anycast selects one destination, while broadcast reaches every eligible host.

For example, IPv6 Neighbor Discovery uses ICMPv6 multicast instead of an ARP broadcast. A host sends a Neighbor Solicitation to a multicast group associated with the target address, and the target responds with a Neighbor Advertisement.

IPv6 Address Types at a Glance

Unicast Addresses

A unicast address identifies one interface and supports one-to-one delivery. A host can have several unicast addresses on one interface. For example, a PC might use a link-local address for local-link operations, a global unicast address for Internet communication, and a unique local address for internal applications.

Anycast addresses use the same format as unicast addresses. An anycast address is assigned to multiple interfaces, but routing causes a packet to reach only one of those interfaces. There is no special anycast prefix that identifies an address as anycast on the wire.

Global Unicast Addresses

A global unicast address is a publicly routable IPv6 unicast address. It is used for communication that may cross organizational networks and reach the Internet. The commonly assigned global unicast range is 2000::/3.

A typical global unicast allocation is organized into three logical parts:

• Global routing prefix: identifies an allocation or larger routed organization.
• Subnet ID: identifies a subnet within that allocation.
• Interface ID: identifies the interface portion of the address on that subnet.

The common subnet boundary is /64. A /64 leaves 64 bits for the interface ID and is important for common IPv6 host-addressing methods such as SLAAC. The /64 convention is not identical to an IPv4 subnet mask, even though both are written with a prefix length.

2001:db8:100:1::10/64 is a documentation-style example of a global-unicast-shaped address. The 2001:db8::/32 documentation range is intended for examples and should not be treated as a production Internet address.

Global unicast addressing is broadly comparable to public IPv4 addressing because both can be routed across the public Internet. IPv6 allocation hierarchy, automatic configuration, the common /64 boundary, and the normal presence of link-local addresses make the configuration model different from IPv4.

Link-Local Addresses

A link-local address is valid only on the local Layer 2 link, such as one Ethernet segment or VLAN. Link-local addresses use the prefix FE80::/10. IPv6-enabled interfaces require a link-local address, even when the interface also has global or unique local addresses.

Routers do not forward packets with a link-local source or destination beyond the local link. A link-local address can therefore be used by two directly connected devices, but not as the destination for communication across a router.

Common operational uses include:

• Neighbor Discovery and address resolution.
• Router Solicitation and Router Advertisement messages.
• Routing-protocol neighbor relationships.
• Default-router next-hop addressing.
• Local-link testing and management.

A router may advertise a global prefix while hosts use the router's link-local address as the default gateway next hop. This is normal: the global address provides broader reachability, while the link-local address provides a stable next hop on the directly connected link.

Because the same link-local value could exist on different interfaces, a host command may require a zone ID, also called an interface qualifier. On Linux, an interface name follows a percent sign:

ping -6 fe80::1%eth0

IPv4 APIPA addresses are a limited familiarity aid for understanding local-only addressing, but the comparison has an important limit. IPv4 APIPA commonly indicates that normal address configuration failed. IPv6 link-local addressing is normal and essential, not merely a failure fallback.

Unique Local Addresses

Unique local addresses, or ULAs, are intended for private use inside an organization or a limited set of cooperating organizations. They use FC00::/7; locally assigned ULA space commonly uses FD00::/8.

ULAs are similar to IPv4 private address space such as RFC 1918 addresses. Internal routers can advertise and route ULA subnets within an organization, but ULA prefixes are not intended to be advertised on the public Internet.

For example, an organization could use fd12:3456:789a::/48 for internal services and divide it into /64 subnets. An internal route might carry fd12:3456:789a:20::/64, while the Internet edge prevents that prefix from being announced to public peers.

ULA and link-local addressing serve different purposes:

• ULA: private but routable across the organization's internal routers.
• Link-local: restricted to one Layer 2 link and never routed beyond that link.

Multicast Addresses

A multicast address identifies a group rather than one interface. IPv6 multicast addresses use the prefix FF00::/8. Membership is dynamic: interfaces join or leave groups, and multicast traffic is delivered to the current members.

IPv6 uses multicast extensively because it has no broadcast address. Important examples include:

• FF02::1: all IPv6 nodes on the local link.
• FF02::2: all IPv6 routers on the local link.

The second part of these addresses represents a multicast scope. At a conceptual level, interface-local scope stays on one interface, while link-local scope stays on one Layer 2 link. Other scopes can support broader multicast distribution when appropriate routing is available.

Neighbor Discovery and Solicited-Node Multicast

A solicited-node multicast address is a multicast group associated with an IPv6 unicast or anycast address. Neighbor Discovery uses it for address resolution and duplicate address detection.

When a host needs the Layer 2 address of an IPv6 neighbor, it sends an ICMPv6 Neighbor Solicitation to the target's solicited-node multicast group. The target answers with a Neighbor Advertisement. This is more selective than an IPv4 ARP broadcast because hosts listen to multicast groups related to their own addresses rather than every host receiving a broadcast.

Anycast Addresses

Anycast is one-to-nearest delivery. The same address is assigned to multiple interfaces, usually on different routers, sites, or service nodes. Routing advertises reachability to each instance and selects one eligible destination, normally the topologically nearest according to routing metrics.

Anycast addresses come from the unicast address space and have no unique prefix that identifies them as anycast. The meaning comes from how the address is assigned and advertised, not from a special address format.

Common uses include:

• Redundant DNS resolvers in multiple sites.
• Distributed service endpoints.
• Gateway redundancy patterns.
• Improving service availability by providing multiple reachable instances.

Anycast does not guarantee the geographically nearest server. It selects according to routing, which may prefer a topologically shorter path rather than physical distance. It also does not automatically provide equal load distribution.

Anycast differs from multicast in a fundamental way: anycast reaches one member of a set, while multicast reaches all current members of a group. Every anycast instance should provide consistent service behavior. Stateful services require session persistence, shared state, or an architecture that can tolerate movement between instances.

Anycast Routing Considerations

• Advertise the shared service address from every intended site or node.
• Ensure routing policy and failure withdrawal behave correctly.
• Use equivalent service data and configuration on all instances.
• Consider convergence events that may move an active client to another instance.
• Do not treat a generic repeated-address configuration as universally safe; the routing design must support it.

Special IPv6 Unicast Addresses

Unspecified Address: ::

The unspecified address is ::, or ::/128. It means that a usable source address is not yet known or assigned. A host may use it temporarily while determining its address configuration, but it is not assigned as a normal destination address.

Loopback Address: ::1

The loopback address is ::1. It refers to the local host and is useful for testing the local IPv6 protocol stack:

ping -6 ::1

Loopback is not the same as link-local addressing. Loopback never leaves the host, link-local addressing reaches directly connected neighbors, and global or ULA addressing can support routed communication within their intended scope.

IPv4 and IPv6 Delivery Method Comparison

Common IPv6 Prefix Recognition

Scope and Routing Comparison

IPv6 Addressing on a LAN

Consider a PC with these addresses:

fe80::a
2001:db8:100:10::a/64

The PC uses fe80::a for local-link operations and can use 2001:db8:100:10::a/64 for communication within the global addressing design. The router's link-local address can serve as the default gateway next hop. The router forwards traffic destined for a global unicast address when a route exists, but it does not forward traffic whose destination is fe80::a beyond the local link.

CCNA-Level Cisco IOS Configuration

IPv6 routing must be enabled globally on a Cisco router before it forwards IPv6 packets. The following example assigns a global unicast address to a routed interface:

ipv6 unicast-routing
interface GigabitEthernet0/0
 ipv6 address 2001:db8:100:10::1/64
 no shutdown

A ULA can be assigned to an internal interface in the same general way:

interface GigabitEthernet0/1
 ipv6 address fd12:3456:789a:20::1/64
 no shutdown

Verify configured and automatically present link-local addresses with:

show ipv6 interface brief
show ipv6 interface GigabitEthernet0/0
show ipv6 route

On Linux, inspect IPv6 addresses and routes with:

ip -6 addr show
ip -6 route show
ping -6 ::1
ping -6 fe80::1%eth0

Troubleshooting IPv6 Address Types

Link-local ping fails or is ambiguous

• Check whether the command includes an outbound interface or zone ID. For Linux, use ping -6 fe80::1%eth0.
• Confirm that the destination is on the same Layer 2 link.
• Verify that IPv6 is enabled and the interface is operational.
• On Cisco devices, identify the relevant interface when the platform requests it.

Hosts on the same LAN cannot resolve one another

• Check whether ICMPv6 Neighbor Discovery traffic is being filtered.
• Confirm that both hosts are in the intended VLAN and IPv6 /64.
• Inspect neighbor tables and check for duplicate-address detection problems.
• Ensure solicited-node multicast and required ICMPv6 messages are permitted.

A ULA cannot reach an Internet destination

• Remember that ULA space is not publicly Internet routable.
• Use a global unicast address for public Internet communication.
• Verify that the host has a default route and a globally usable prefix.

A link-local address works locally but not remotely

• Link-local traffic cannot cross a router boundary.
• Use a global unicast or ULA destination for routed communication.
• Confirm the intended route and the scope of the destination address.

Anycast clients experience changing sessions

• Routing changes may move traffic between anycast instances.
• A stateful service may fail if session state is not shared or preserved.
• Verify route advertisements, convergence behavior, and equivalent service configuration.
• Use state synchronization, persistence, or another service architecture when the application cannot tolerate instance changes.

Key Points to Remember

• IPv6 has three top-level delivery types: unicast, multicast, and anycast.
• IPv6 has no broadcast addresses; multicast handles many functions that used broadcast in IPv4.
• Global unicast commonly uses 2000::/3 and is intended for public routing.
• Link-local addresses use FE80::/10, are required on IPv6-enabled interfaces, and stay on one link.
• ULA addresses use FC00::/7, commonly FD00::/8, and can be routed internally but not on the public Internet.
• Multicast uses FF00::/8 and delivers to all members of a group.
• Anycast uses unicast-format addresses and delivers to one routing-selected instance.
• ::1 is loopback, while :: is unspecified and is not a normal destination.
• A /64 is the common IPv6 subnet boundary and supports common SLAAC operation.

For the related structure of IPv6 addressing, continue with IPv6 address types and scope.