MAC address vs IP address: what each one tells you

Short answer: a MAC address identifies the physical device — it’s assigned by the manufacturer and mostly stays fixed. An IP address identifies where that device sits on a network right now, and it can change every time the device reconnects.

MAC address: the device’s own ID

Every network interface — a phone’s WiFi chip, a laptop’s ethernet port, a smart plug’s radio — has a MAC (Media Access Control) address burned in at manufacture. It’s a 12-character string like 3C:5A:B4:12:9D:E7, split into two halves. The first half is the OUI, a block registered to the manufacturer. The second half is unique to that specific unit.

A MAC address only means anything on the local network segment. It doesn’t route across the internet, and your ISP never sees it. Routers use it to tell devices apart on the same WiFi or ethernet, which is why your router’s client list shows a MAC next to every connected device.

One wrinkle: most phones and modern laptops now generate a random MAC address per network instead of broadcasting the real one. That’s a deliberate privacy feature, not a bug, and it means the address you see in a client list isn’t always the one printed on the device. Randomized MAC addresses cover how to spot one.

IP address: where the device is right now

An IP address is a location, not an identity. Your router assigns one to each device when it joins the network, usually via DHCP, and reuses that same address pool for whatever connects next. Reboot the router, and devices often come back with different IPs. Leave the house and join a coffee shop’s WiFi, and the device gets a completely different address on a completely different network.

There are two layers to this. Your local IP (something like 192.168.1.42) only means something inside your own network — it’s how your router tells your laptop from your smart TV. Your public IP is the address your whole household shares with the outside internet, assigned by your ISP, and it’s what a website sees when you visit it.

Why you need both

A MAC address without an IP address can’t send or receive traffic on the internet. It’s stuck at the local link layer. An IP address without a MAC address doesn’t exist on a physical network at all, since something still has to answer for that address on the wire. The two work together: the MAC gets a packet to the right physical device on the local network, and the IP gets it there and back across the wider internet.

This is also why they solve different problems when something goes wrong:

• Troubleshooting a specific device losing connection — look at its IP first. A duplicate or expired IP address is a common cause.
• Figuring out what a device actually is — look at its MAC. The vendor OUI often tells you more than a name like “android-4f2b1a” ever will. Look up a MAC’s vendor here.
• Blocking a device for good — use MAC filtering. An IP-based block only holds until the device requests a new address, which can happen automatically.
• Setting up port forwarding or a static reservation — this is IP territory, since it’s about where traffic gets routed, not which physical device answers.

Seeing both at once

Open your router’s admin page and the connected-devices list shows both side by side: a MAC address for each device, next to whatever IP it currently holds. That pairing is temporary — the router remembers which MAC got which IP for as long as the lease lasts, then can hand that IP to a different device later. If you want a device to always get the same local IP, most routers let you set a static DHCP reservation tied to its MAC address specifically, so the two stay linked even across reboots.

If you’re staring at that list trying to work out which row is which physical device, that’s really a MAC-address question. How to identify a device from its MAC address walks through matching an unfamiliar entry to something you actually own.