MAC address randomization

MAC address randomization. A practical guide for network diagnosis and careful interpretation. One technical signal does not describe the whole path, so each connection layer should be checked independently and in a reproducible order.

What happens at the link layer

MAC address randomization concerns interface identifiers inside a local Layer-2 segment. A MAC address is not a globally routed user identifier: it can be changed or randomized, and routers do not carry the end device MAC address across the Internet.

How to interpret a MAC address

Vendor lookup relies on registered address prefixes, so it can describe a factory address without proving the manufacturer of a particular device. A locally administered address or Wi-Fi randomization can intentionally make an OUI lookup uninformative.

Concrete examples and values

Use these values as anchors when reading documentation or test output: locally administered MAC; per-network address; Wi-Fi privacy; vendor lookup limits.

Check whether the U/L bit marks a locally administered address and compare reconnects to the same SSID; modern clients may keep one randomized address per network rather than changing it on every packet.

Common causes and mistakes

A common mistake is to treat one successful test as proof that the whole path is healthy. A reachable IP address does not prove DNS works, an open port does not validate the application protocol, and a fast speed test does not rule out latency, packet loss, or Wi-Fi contention. NAT, CGNAT, firewalls, CDNs, Anycast, and caches can also change what an observer sees and must be considered according to the question.

What the result does not prove

A technical result has limits. It normally cannot establish a person’s identity, the owner of a device, or the single root cause of an outage without additional evidence. IP geolocation is approximate, registration data can be redacted, and Internet routes can change. Security should not be reduced to one flag, address, or status value. A conclusion should match the specific property that was actually measured.

A reproducible troubleshooting sequence

Begin with a reproducible symptom, then verify local configuration, addressing, and DNS. Continue with routing, ports, and the application protocol. Make one change, repeat the measurement, and compare the outcome. This sequence reduces false conclusions and produces useful evidence for an administrator or Internet provider. After fixing the problem, repeat the original test to confirm that the observed symptom, rather than an unrelated condition, actually changed.