Link-local address
What is Link-local address?
A link-local address is an IP address that only works on its own local network segment and is never routed anywhere else -- IPv6 assigns one automatically in fe80::/10, while IPv4 falls back to 169.254.0.0/16 via APIPA when DHCP fails. AdminKit's guide to IPv6 SLAAC and EUI-64 addressing covers how these get generated and used.
By AdminKit team, Netbase JSC · Updated
A link-local address is an IP address valid only on the local network segment it was configured on, never routed beyond it. In IPv6, every interface automatically generates one in the fe80::/10 block defined by RFC 4291 and listed in IANA’s IPv6 Special-Purpose Address Registry, using it for essential local operations like neighbor discovery and SLAAC (RFC 4862) before any routable global address is even assigned. IPv4 has an equivalent mechanism, RFC 3927’s 169.254.0.0/16 range, which a device assigns itself via APIPA when DHCP fails, as a fallback rather than a routine addressing scheme — Microsoft’s own documentation on automatic TCP/IP addressing describes the same APIPA fallback behavior in Windows. Because link-local addresses aren’t globally unique or routable, the same fe80:: address can appear on many different interfaces at once, which is why IPv6 tooling and URLs require a zone index (such as fe80::1%eth0) to say which interface it applies to; on Linux, the ipv6(7) manual page notes that the socket address’s sin6_scope_id field is supported only for link-local addresses, where it carries that interface index. Unlike a ULA, which is routable across an entire private network, a link-local address never leaves the single segment it was generated on, which is why IPv6 networks commonly use both for different scopes of private addressing. AdminKit’s guide to IPv6 SLAAC and EUI-64 addressing covers how link-local addresses get generated and used during IPv6 autoconfiguration.
Link-local addresses are also what Neighbor Discovery Protocol messages use for address resolution on the local segment, the IPv6 successor to ARP.
To confirm whether a specific address you’re looking at is actually link-local (rather than some other reserved range), paste it into AdminKit’s IP info tool for an offline classification.
Link-local address is part of AdminKit’s IP & network cluster; the full AdminKit glossary lists other related terms.
Frequently asked questions
Does a link-local address work the same way in IPv4 and IPv6?
Not quite -- IPv6 assigns one automatically on every interface in fe80::/10 for essential local operations, while IPv4 only falls back to its 169.254.0.0/16 range via APIPA as a last resort when DHCP fails.
Why do IPv6 URLs sometimes need a zone index, like fe80::1%eth0?
Because link-local addresses aren't globally unique or routable, so the same fe80:: address can appear on many different interfaces at once -- the zone index says which interface it applies to.
What's the difference between a link-local address and a ULA?
A ULA is routable across an entire private network, while a link-local address never leaves the single segment it was generated on -- which is why IPv6 networks commonly use both for different scopes of private addressing.
What RFC defines IPv6 link-local addressing?
RFC 4291 defines the fe80::/10 link-local block as part of the IPv6 addressing architecture, with SLAAC (RFC 4862) one of the first things a device uses it for before any routable address is assigned.