IPv6 EUI-64: The Address Nobody Configured
An interface address the router invented from its own MAC, and the documentation only guessed. Diagnose it and configure the intended address yourself, live, right below.
Symptom
The documented address does not answer and the interface is perfectly healthy. The router built its own address out of the hardware, and whoever wrote the record guessed.
Your mission
Prove the cause, then fix it
Format
Guided CLI investigation
Investigate before you configure.
Use the CLI evidence to isolate the fault, make the smallest safe correction, then verify the network state changed.
Observe the symptom and link state.
Diagnose by comparing the protocol evidence.
Verify the expected device state and confirm the original symptom is resolved.
Console access: R1
This workspace stacks for portrait phones. Rotate to landscape for the full split-screen console.
Need a hint?
Reveal the root cause when you're ready.
Try the investigation first, then use this as your escape hatch, not a dead end.
Lab debrief
Turn the session into a repeatable troubleshooting pattern.
Use this reference after your attempt: first explain the symptom, then verify the evidence, then confirm the repair.
The problem
The IPAM system records R1's Gi0/0 address as 2001:DB8:ACAD:1::1. Nothing at that address answers and a colleague has escalated it as an interface fault, but the interface is up and its configuration has not been touched.
What you'll practice
- Read the address an interface actually holds rather than the one documented
- Derive an EUI-64 interface identifier from a MAC address
- Explain why the seventh bit of the first byte is inverted
- Recognise the same identifier inside the link-local address
1. The prefix is not the address
Writing 2001:DB8:ACAD:1::/64 with eui-64 tells the router the first half and lets it build the second half itself. You will learn to read a configuration line like that as a rule rather than as an address.
2. Doing the arithmetic in both directions
Split the MAC, insert FFFE, flip one bit. You will work through it once by hand and then be able to recognise an EUI-64 address on sight, including spotting when a device is not using one.
3. Why the bit flips
In a MAC address that bit means locally administered; in an IPv6 interface identifier the sense is inverted so a burned-in address produces a 1. It is purely a convention mismatch between two standards, and it is the step people forget.
The topology
A single router, R1, with Gi0/0 configured using the eui-64 keyword on the 2001:DB8:ACAD:1::/64 prefix.
Commands to run yourself
The real diagnostic commands for this lab, copy-paste ready. Run these in the same order to reproduce the investigation on your own session.
show ipv6 interface briefshow ipv6 interface GigabitEthernet0/0show interfaces GigabitEthernet0/0Topology diagram
Frequently asked
Why is the address not 2001:DB8:ACAD:1::1?
Because nobody configured that address. The configuration supplies a /64 prefix and the eui-64 keyword, which tells the router to derive the host half of the address from its own MAC. The ::1 form is a reasonable guess for a manually numbered gateway and simply is not what this interface was told to do.
Why do the global and link-local addresses share a second half?
Because both are built from the same interface identifier. The link-local address is FE80:: followed by that identifier, and the global address is the configured prefix followed by the same identifier. Noticing they match is usually the fastest way to spot that EUI-64 is in play.
Is EUI-64 still recommended?
It is fine for infrastructure interfaces and it is very common on router links, but it does embed the MAC address in the IPv6 address, which is a privacy concern for client devices. That is why hosts generally use privacy addressing or randomly generated identifiers instead, while routers are usually numbered manually or with EUI-64.
Ready to run this lab yourself?
No setup, no image sourcing. Book a session or ask for a live demo.