MAC Address

What is a MAC address?

A MAC (Media Access Control) address is the hardware identifier assigned to a network interface — the 48-bit address (written like 00:1A:2B:3C:4D:5E) burned into your laptop’s Wi-Fi card, your phone’s radio, a server’s NIC. It operates at Layer 2 (the data link layer) of the networking stack and is used to deliver frames between devices on the same local network segment. It’s the counterpart to the IP address, which operates at Layer 3 and is what actually routes traffic across networks to reach a global destination. Understanding the division of labor between them is the whole point of learning what a MAC address is.

MAC vs IP — local delivery vs global routing

This is the concept that matters, and it’s where most confusion lives. An IP address is logical and routable: it’s assigned by the network, can change (you get a different IP on Wi-Fi at home vs at a café), and routers use it to move packets across the internet toward the right destination network. A MAC address is physical and local: it identifies a specific interface on the local segment and is used only for delivery within that segment — it is not routable across the internet and routers do not forward based on it. The analogy that sticks: the IP address is like the postal address on an envelope (gets it to the right building anywhere in the world), while the MAC address is like “hand it to the specific person in this room” (only meaningful locally). They work together on every hop: when your device wants to send to an IP on its local network, it uses ARP (Address Resolution Protocol) to discover the MAC address behind that IP, then addresses the frame to that MAC. As the packet crosses each router, the IP addresses (source/destination) stay the same end-to-end, but the MAC addresses are rewritten at every hop to the next link’s interfaces. That’s the key mental model: IP is end-to-end, MAC is hop-to-hop.

Where it actually matters — and modern wrinkles

For most cloud and application engineers, MAC addresses are mostly invisible plumbing — the cloud provider’s virtual network handles Layer 2, and you work with IPs, subnets, and security groups. But MAC awareness shows up in real places: network security (MAC filtering on Wi-Fi, port security on switches, though MACs can be spoofed so this is weak as a sole control), DHCP (the DHCP server often uses the MAC to assign or reserve a consistent IP for a device), and software licensing (some licenses bind to a MAC as a machine fingerprint). A modern wrinkle worth knowing: because a fixed MAC lets networks track a device across locations, phones and laptops now use MAC randomization — presenting a random MAC per network for privacy — which occasionally breaks MAC-based allow-lists and confuses admins who assumed MACs were stable identifiers. The recurring misconceptions: thinking MAC addresses route traffic across the internet (they don’t — that’s IP), treating MAC filtering as strong security (MACs are trivially spoofable), and assuming a device’s MAC is permanent (randomization and virtualization both undermine that).

What people get wrong

• Thinking MAC addresses route across the internet — they’re local (Layer 2, hop-to-hop); global routing is done by IP addresses (Layer 3, end-to-end).
• Relying on MAC filtering for security: MAC addresses are easily spoofed, so they’re a weak control, not a real access barrier.
• Assuming MACs are permanent — MAC randomization (privacy) and virtualization mean the “burned-in” address you count on may not be stable.

Primary source: IEEE 802 / MAC address overview (MDN networking)