Practical tools for system, network, security, and operations administrators.

NET-C0075 · IP & Internet Intelligence

MAC Address Randomization and Its Impact on Networks

Expect randomized MAC addresses on a wireless LAN you administer, and do not try to defeat them.

Updated 25 October 2026 · Explainer

This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.

What this hour is for

Modern clients can present a different MAC per network, or rotate it. DHCP reservations and port security that assumed a stable hardware address will not see the same client twice. That is the impact on a network you run.

The checker and the generator help you recognize a local administered bit or draft a lab MAC. They are not a way to follow a person across random addresses. Do not build a correlation. Do not collect client MACs to identify someone.

Write the new operational habit: authenticate the user or the device with 802.1X if you need a stable identity, and stop keying policy on the MAC alone. One WLAN. The 802.1X page owns the deployment.

The change you can finish

Apply nothing during the writing of the note. When the lab window opens, it is one change on the device named in the ticket. Read the draft, then the device, then decide.

Rollback is the file or the revision you saved first. You do not invent a rollback after the only copy is gone.

  1. Name the WLAN you administer.
  2. Write which controls still assume a stable MAC.
  3. Pick one control to change later.
  4. Do not correlate random addresses.
  5. Do not collect clients to identify a person.
  6. Stop.

Mistakes that outlive the command

MAC Address Randomization and Its Impact on Networks goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.

Decisions to write down

One decision for MAC Address Randomization and Its Impact on Networks: The WLAN is yours. The broken assumption is named. Identity, if needed, is 802.1X later. No person was tracked. And no client list was harvested.

Checks before you call it done

Confirm this before you call the change done: One WLAN is in the note. One broken control is named. No correlation was attempted. No addresses were harvested. And the next change is a separate ticket. If one of those fails, stop.

Before you leave the device

MAC Address Randomization and Its Impact on Networks ends when the hostname on the device matches the hostname in the ticket. If it does not, you are on the wrong box. Stop. A command that succeeded on the wrong box is not progress.

The draft stays a draft until a person has read the names in it. A generator does not log into the device and does not know which interface is the uplink. You delete a line that names a device, a zone, or a prefix you did not write down.

0.0.0.0/0 is not kept because a sample included it. A source you can say is the source you keep. 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. They belong in the note. They are not prefixes you type onto a production device because they appeared in a draft.

prompt-for-this is a reminder that a secret is missing. It is not a password, a key, a community string, or a pre-shared key you save in the ticket or in git. The real secret stays in the store.

One change is the window. A VLAN and a routing protocol and a VPN do not share it. If two things move and the result is wrong, you will not know which one did it. The next feature waits for its own page.

If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied config produces a device nobody can rebuild. Restore the copy you took first.

A second person reads the device name and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the device alone.

This page is a planning guide. It is not a vendor manual, not an official standard, and not a permission to touch a network you do not administer. The pillar guide owns the wider design. This page owns one lab proof.

Tools for this guide

These tools run in the browser on this site. They do not log into your machines.

More in this cluster

The pillar for this page, and the next published pages filed with it.