MAC addresses and ARP — finding one device on the local network

Every lesson so far has treated "the destination IP address" as the thing that gets a packet where it's going. That's true across the internet, hop by hop between routers — but it's not the whole story for the very last step, getting a packet from your router onto the one physical device it's actually meant for.

That last step uses a completely different kind of address: a MAC address (Media Access Control address) — a 48-bit identifier burned into every network interface at the factory, written like 3c:22:fb:8a:9e:01. Unlike an IP address, a MAC address isn't routable across networks at all — it only means anything on the one local network segment a device is physically connected to.

Say your laptop already knows it wants to reach 192.168.1.5 on your local network (maybe a printer). It knows the IP — but to actually put a frame on the wire, the network card needs the destination's MAC address, and it doesn't have it yet. ARP (Address Resolution Protocol) is the mechanism that fills in that gap:

You can see this cache yourself — arp -a on most operating systems lists every IP-to-MAC mapping your machine has already resolved.

This is also the concrete reason a router is necessary at all. If you send traffic to a device outside your local network, ARP can't help — that device isn't on your local wire, so it can never reply to a broadcast. Instead, your machine ARPs for its default gateway (your router) and hands the packet to it; the router repeats a fresh ARP lookup on whatever network the destination actually lives on, one hop at a time — the same hop-by-hop idea from the very first lesson in this domain, just now with a name for what happens at each hop.