This is an idle thought that I didn’t finish, but accidentally posted instead of another post yesterday, so I’m gonna fix.
There are thoughts that computer professionals ask that other people don’t, and as long as we only ask these things of ourselves and other computer professionals, we won’t be thought of as too weird.
In this case, the thought that came to me as I packed up to go to my local coworking space, was “How many MAC addresses are on me right now?”
MAC stands for Media Access Control is is how computers identify each other over the network. Instead of diving into the magic of ARP…
You go to your favorite coffee shop and order a latte. They ask for your name, write it on the cup, and start to prepare your caffeinated drink.
Eventually, after the brewing and the pouring and all, they call out the name you gave, and you come to collect the beverage.
MAC addresses serve as your device’s name in the networking context. It cannot receive the packets (the “coffee” in the metaphor) unless it answers to the name it gave.
“…the name it gave.”
I emphasize this because it doesn’t have to be your name, or any name you have ever had. At a conference last year, I organized a “Dave BOF” after realizing that there were at least five other Daves in the conference, my name is so common. So I often give the name “Clem” at coffee shops, because that name’s rare.
And let’s dive down on it a bit. These things are unique to the networking device, which means if you switch your cards to another computer (which, in the days of desktop computers, I used to do), that MAC address went with it. In our coffee shop metaphor, I might generally say “Clem”, but go by “Larry” to the barista who is a bit too much of a Buffy the Vampire Slayer fanboy.
In a less metaphorical sense, I’ve heard stories of high-availability servers have their fail-over machines replicate their MAC addresses, so that the traffic never stops. It strikes me that, with Kubernetes and load-balancing and everything we’ve developed in the last 20 years, this is not something we do with new systems, but I could be wrong.
Headphones: Bluetooth. 1 MAC.
FitBit: Bluetooth. 1 MAC.
Android Tablet: Bluetooth and WiFi. 2 MACs.
Bluetooth keyboard: Bluetooth. Duh. 1 MAC.
Laptop: Bluetooth and WiFi. 2 MACs.
USB-to-Wired-Ethernet dongle. 1 MAC.
Logitech Unifyng dongle: Unifying is like Bluetooth but different. We’ll say 1 MAC.
Logitech presentation remote: I know that these things have unique dongles, use non-IR protocols so line-of-sight isn’t required, and for this to be true, it must use some sort of pre-Unifying networking protocol, so I have to assume 2 MACs , for the dongle and device, although I cannot prove it.
Raspberry Pi Zero: I put it together as a conference nametag. It’s a full computer, more powerful than many I used professionally in my life, and I used it to run an e-ink display. Anyway, it is in my backpack, and has onboard WiFi and Bluetooth. 2 MACs.
Android Phone: Here we get a new one. It has Bluetooth (I’m listening to Purple Rain on the above-mentioned headphones over Bluetooth), and WiFi, but it can also talk to my cellular provider’s data network. I have to say 3, but there’s a digression from what I’ve seen.
Should I count MEID/IMEI?
So, 16 uniquely-identifying numbers that my devices throw around.
1X/3G/4G interfaces on cellular devices do have a MAC address, but those MACs are dynamically assigned and change on every reboot of the device… this is because MAC addresses only apply to IEEE 802 technologies, of which cellular networks are not.
So yes, cellular networks are dynamically assigned a MAC address on a smartphone when that device is powered on or rebooted, however, these dynamically assigned MACs cannot be used in a firewall (it would literally be pointless to do so).
This is answering a question that isn’t ours, but it seems that, for some of our cellular networking protocols, your device is not permanently unique.
This can be good: Your phone checks for cells, and those are logged and can be used to track you. iOS creates a random MAC for this. (I deleted the link to the source on that one; sorry!)
So, I might get to dock one.
Maybe you shouldn’t. As I pointed out when I started this, this is just geeky weirdness that will make your eyes glaze over.
TCP/IP. We can skip the Bluetooth and Logitech MACs for a moment to point out that there are five MACs – tablet WiFi, phone WiFi, laptop WiFi, wired networking dongle and phone cellular – that also need an IP address. More than one, as they’re all mobile and moved between home, office, coffee shop and co-working space. With IPv4 networking, there are 4,294,967,296 available addresses. We wallpaper over this a lot with NAT, but the big solution is to move to IPv6, which we, by and large, haven’t done. This is computing’s current impending-disaster-we’re-ignoring-for-now. Or at least one of them.
Tracking. This is the most important one, to the right people. If I’m sniffing for Bluetooth devices and looking for my boss’ fitness tracker, so I know that he’s right behind me while I’m coding or blogging, that’s one thing, but if instead, it’s a retail location identifying repeat shoppers by sniffing for BT and WiFi, it’s perhaps a little bit more suspect, and if it’s an angry ex, putting a sniffer along an exercise trail to determine the other’s schedule in order to plan something dire, we’ve gone into dangerous territory.
As Leslie Carhart wrote, “Knowing your personal threat model is important!”, and your health and connectivity might trump these issues, but I really think this is something you should consider.