Why Does My Device Have Three IPv6 Addresses? A Guide to Link-Local, Public, and Privacy Addresses
Content
## The Scenario
After enabling IPv6 on your home network, you might be surprised to find that a device, like a NAS or a PC, has been assigned multiple IPv6 addresses. For example, a user found their NAS had the following three addresses and was curious about their functions:
```plaintext
240e:3a3:6e2b:5e00::f5e/128
240e:3a3:6e2b:5e00:2697:edff:fe18:92c4/64
fe80::2697:edff:fe18:92c4/64
```
Having three IPv6 addresses is perfectly normal. It's a clever design of the IPv6 protocol to balance connection stability, public accessibility, and privacy. Here, DP@lib00 will break down what each of these addresses means and what it's used for.
---
## 1. `fe80::2697:edff:fe18:92c4/64` - The Link-Local Address
* **Type:** Link-Local Address
* **Identifier:** Always starts with `fe80::`.
* **Purpose:** This is the most basic IPv6 address, automatically generated by every IPv6-enabled network interface. It is **only used for communication within the local network (LAN)**. It cannot be used to access the internet, and routers will not forward traffic from this address to the public internet. Its main functions include device discovery on the local network, Neighbor Discovery Protocol (NDP), and other low-level auto-configuration tasks. You can think of it as the more powerful and mandatory equivalent of the `169.254.x.x` address in IPv4.
---
## 2. `240e:3a3:6e2b:5e00:2697:edff:fe18:92c4/64` - The Stable Global Address
* **Type:** Global Unicast Address (GUA), generated using the EUI-64 standard.
* **Breakdown:**
* **Network Prefix** (`240e:3a3:6e2b:5e00`): This part is the public network segment assigned by your Internet Service Provider (ISP) to your home network (e.g., your `wiki.lib00` router).
* **Interface Identifier** (`2697:edff:fe18:92c4`): This part is automatically calculated from your NAS's network card MAC address (`24:97:ed:18:92:c4`) using the **EUI-64 specification**. This standard expands the 48-bit MAC address into a 64-bit identifier by inserting the fixed `ff:fe` string in the middle.
* **Purpose:** This is a **stable and permanent public IP address**. Because it's derived from the hardware MAC address, it will not change unless you replace the network card in your NAS. Its primary use is **as a server address**. When you want to access your NAS from the internet (e.g., for a website, file server, or remote management), this is the address you should use. You would configure firewall rules on your router to allow traffic to this address. In a `lib00` network setup, this is the key address for public services.
---
## 3. `240e:3a3:6e2b:5e00::f5e/128` - The Temporary/Privacy Address
* **Type:** Temporary Global Unicast Address (Temporary GUA) or Privacy Address.
* **Breakdown:**
* It uses the same public network prefix (`240e:3a3:6e2b:5e00`) from your ISP.
* However, its interface identifier (`::f5e`) is a **randomly generated, non-predictable, and often shorter string**.
* **Purpose:** The main goal of this address is to **protect your privacy**. When your NAS initiates outbound connections to the internet (e.g., to check for software updates or download files), it uses this temporary address as its source address by default. Because this address is random and changes periodically (often daily), external websites and services cannot use it to track your specific device or its activity over the long term. This prevents the privacy risks associated with exposing a fixed, hardware-based public IP.
---
## Summary: Why Three Addresses?
Your device has three addresses to achieve a separation of concerns, providing an optimal balance of compatibility, stability, and security:
1. **Link-Local Address (`fe80::...`)**: Handles fundamental **internal LAN communication** and device coordination.
2. **Stable Global Address (`240e:...:2697:edff:fe18:92c4`)**: Acts as the **"server" address**, providing a reliable and fixed entry point for inbound connections from the internet.
3. **Temporary Privacy Address (`240e:...::f5e`)**: Acts as the **"client" address**, protecting your privacy during outbound connections by masking your device's identity.
In simple terms: one for internal chatter, one to be the public "target" (server), and one to be the "disguise" (client) when venturing out. When configuring your firewall or DNS records for public access to your device, always use the **stable global address** that contains `edff:fe`.
Related Contents
IPv6 Demystified: Can You Still Use Ports with DDNS Like in IPv4?
Duration: 00:00 | DP | 2025-12-09 12:13:20The Ultimate Guide: Solving Google's 'HTTPS Invalid Certificate' Ghost Error When Local Tests Pass
Duration: 00:00 | DP | 2025-11-29 08:08:00The Ultimate Guide to Storing IP Addresses in MySQL: Save 60% Space & Get an 8x Speed Boost!
Duration: 00:00 | DP | 2025-11-10 17:51:00Recommended
PHP Case Conversion Mastery: `strtolower()` vs. `mb_strtolower()` - Are You Using the Right One?
00:00 | 10Converting uppercase strings to lowercase is a fun...
The Ultimate Guide to Centering in Bootstrap: From `.text-center` to Flexbox
00:00 | 7Struggling with centering elements in Bootstrap? T...
Vue's Single Root Dilemma: The Right Way to Mount Both `<header>` and `<main>`
00:00 | 7A common challenge in Vue development is controlli...
Decoding MySQL INSERT SELECT Errors: From Syntax Traps to Data Truncation (Error 1265)
00:00 | 4Ever encountered frustrating syntax errors or the ...