The Off-Key Bard
Technology

What Is a MAC Address, and Why Does Every Device Have One?

Or: your router needs to know which device is actually which. MAC addresses and IP addresses look similar but solve completely different problems.

Or: Your Router Needs to Know Which Device Is Actually Which

Open the network settings on your computer, phone, or game console and you'll find something that looks like this: A4:5E:60:12:34:56. It's called a MAC address. Despite the name, it has nothing to do with Apple Macs — MAC stands for Media Access Control.

A MAC address is an identifier associated with a specific network interface. Your Wi-Fi adapter has one. Your Ethernet port has one. Your phone has one. Your smart TV has one. Your router has several — one for each of its network interfaces.

This raises an obvious question. You already have IP addresses. If your computer has something like 192.168.1.42, why does it need another identifier?

Because IP addresses and MAC addresses solve different problems.

Two Levels of Addressing

Think of sending a package to an apartment building. The street address — 125 Main Street — gets the package to the right building. But once it arrives, you still need to know: Apartment 4B. Those are two different levels of addressing solving two different parts of the same delivery.

IP addresses work like the street address. They help route traffic across interconnected networks — across the internet — toward the right destination. MAC addresses work like the apartment number. They help devices communicate across the local network link: the immediate Ethernet segment or Wi-Fi network you're on right now.

When data travels across your local network, it's wrapped in an Ethernet frame that contains source and destination MAC addresses identifying where that local transmission came from and where it's going next. This layer of addressing operates beneath the IP networking most people think about.

How ARP Connects the Two

Suppose your computer wants to reach a website. The website lives somewhere out on the internet, so the data needs to go to your router first. Your computer knows the router's IP address — typically something like 192.168.1.1 — but to send a frame across the local network, it needs the router's MAC address too.

This is where ARP — Address Resolution Protocol — comes in. Your computer broadcasts a message to the local network: "Who has 192.168.1.1?" The router responds with its MAC address. Your computer stores that mapping temporarily in an ARP cache and uses it going forward. It's networking's version of: "I know the person's name — which desk are they sitting at?"

This resolution happens automatically, invisibly, every time your computer communicates with a local device it hasn't talked to recently. You can actually see the results: on Windows or macOS, viewing the ARP table (arp -a in a terminal) shows the IP-to-MAC mappings your computer has recently learned.

How Switches Use MAC Addresses

An Ethernet switch connecting multiple wired devices doesn't just blast every frame out of every port — that would be noisy and inefficient. Instead, it builds an internal table associating MAC addresses with the specific ports they've been seen on:

  • Port 1: Desktop (A4:5E:60:12:34:56)
  • Port 2: Game console (18:C0:4D:98:76:54)
  • Port 3: Television (74:32:8A:11:22:33)

As frames arrive, the switch reads their source MAC addresses and updates the table. When traffic is destined for a particular MAC address, the switch forwards it directly to the correct port rather than broadcasting it everywhere. The network learns and adapts as devices are connected, disconnected, or moved — without you drawing it a map.

If a frame arrives destined for a MAC address the switch hasn't seen yet, it floods the frame out to all ports except the one it came from. The intended device receives it and responds, at which point the switch learns where it is. Essentially: "I don't know which port Dave is on — someone go ask. Dave raises his hand. Problem solved."

Are MAC Addresses Permanently Fixed?

Historically, MAC addresses were described as "burned in" to the network hardware — permanent factory-assigned identifiers. This is increasingly incomplete. Operating systems and software can use different addresses than the hardware default, a capability called MAC address spoofing. More relevantly for everyday users, modern devices do this deliberately for privacy.

If your phone always broadcasts the exact same hardware address when connecting to Wi-Fi networks, different networks can recognize: "We've seen this device before." That creates opportunities for persistent tracking even without knowing who owns the device. iOS, Android, and modern desktop operating systems now use private or randomized MAC addresses for Wi-Fi — presenting a different address to each network rather than the same hardware identifier everywhere.

This is useful. It can also cause confusion. If you've configured your home router to always assign the same IP address to your phone based on its MAC address (a DHCP reservation), and your phone starts using a randomized address, the router sees an unknown device and your reservation breaks. Privacy features are useful — they just occasionally make your network settings behave unexpectedly.

A Few Common Misconceptions

Websites can see your MAC address. They generally can't. Routers don't forward local Ethernet frames onto the public internet — they extract the IP packet inside and create new framing for the next network hop. The web server you're connecting to sees your public IP address. Your local MAC address never leaves your local network segment.

MAC address filtering is strong security. Restricting Wi-Fi access to a list of approved MAC addresses offers weaker protection than it sounds. Because MAC addresses are broadcast in plaintext over the air, someone observing wireless traffic can capture an approved address and configure another device to use it. MAC filtering can serve as an administrative convenience; it's not a substitute for WPA2 or WPA3 encryption and authentication.

One device has one MAC address. MAC addresses belong to network interfaces, not to devices as a whole. A laptop with an Ethernet port, a Wi-Fi adapter, and a Bluetooth adapter has three distinct MAC addresses. Virtual machines generate their own virtual MAC addresses. Containers in cloud environments do too — the concept scales all the way from your home router to the infrastructure underlying large cloud platforms.

The Bard's Take

Most people will never need to think about their MAC address. That's how networking is supposed to work — the local addressing happens automatically, invisibly, underneath everything else.

Your computer handles ARP. Your switch learns which devices are on which ports. Your router assigns IP addresses. Your phone may randomize its Wi-Fi MAC address for privacy. You just click Connect.

But underneath that simple button, the network is quietly solving a fundamental problem: everyone on the local link needs to know who is who. IP addresses handle the global routing question — where does this packet ultimately need to go? MAC addresses handle the immediate local question — which device in this room do I hand this to first?

That strange-looking string A4:5E:60:12:34:56 isn't your computer's secret internet identity. It doesn't reach websites. It has nothing to do with owning an Apple computer. It's simply the local identifier that helps networking equipment answer one of computing's most immediate questions: what's the next step in getting this where it needs to go?

Sources

← Back to the Desk — Technology