MAC Address

MAC address (Media Access Control address) is a 48-bit identifier assigned to a network interface controller (NIC) and used to deliver frames within a local network segment. It operates at the data link layer (Layer 2) of the OSI model and is what Ethernet and Wi-Fi actually use to move a frame from one device to the next on the same physical or wireless network. It is usually written as twelve hexadecimal digits, for example a8:3b:9d:1f:42:0e, and is sometimes called the hardware or physical address.

Structure and the OUI

The 48 bits split into two 24-bit halves. The first half is the Organizationally Unique Identifier (OUI), a block the IEEE Registration Authority allocates to a hardware vendor, so the leading digits often reveal the manufacturer of a NIC. The second half is a serial value the vendor assigns to that specific interface. Together they are meant to be globally unique, though MAC addresses can be administratively overridden in software — a bit in the first octet even distinguishes universally administered addresses from locally administered ones, which is how randomization and virtual interfaces announce themselves honestly at the protocol level.

Local scope, ARP, and privacy

A MAC address only has meaning on the local link; routers rewrite the source and destination MAC at each hop, while the IP address stays end-to-end — the clean division of labor at the heart of TCP/IP. The glue between the layers is ARP, which lets a device ask "who holds this IP?" and receive the owner's MAC so the frame can be addressed. Because a fixed MAC can be used to track a device as it moves between Wi-Fi networks — retail analytics built an industry on exactly that — modern phones and laptops support MAC randomization, presenting a different address per network. Worth internalizing: your MAC never crosses the internet, but on any local network you join, it is your name.

Running a mining fleet by MAC

MAC addressing stops being trivia the day you manage more than a couple of machines. Miners ship configured for DHCP, and the reliable way to give each unit a stable identity is a DHCP reservation binding its MAC to a fixed IP — so the machine you labeled rack 2, slot 5 is always reachable at the same address after every power cycle. Fleet-discovery tools work the same way, sweeping the subnet and recognizing miners by their vendor OUI prefixes, and when a hashboard-laden unit goes silent, the DHCP lease table and ARP cache are where you look first. A word of caution from the repair bench: control-board swaps and firmware reflashes can change or clone a MAC, and two devices sharing one MAC on a segment produces maddening intermittent connectivity — check for duplicates before blaming the network.

Segmentation and control

For a sovereign operator, MACs are also the handle for network hygiene: assigning miners and IoT gear to an isolated VLAN, carving address plans per subnet, and applying port-security rules that limit which hardware may speak on a switch port. None of it is exotic — just the Layer 2 plumbing, understood and used deliberately, which is most of what separates a network you run from a network that merely happens to you.

Two field notes save time. Manufacturers print each control board's MAC on a sticker, which is worth photographing during deployment — matching a misbehaving DHCP lease to a physical machine is far faster with a spreadsheet of MACs than by unplugging cables one at a time. And virtualization reuses the locally-administered space heavily: every VM and container interface carries a software-assigned MAC, so a busy hypervisor legitimately answers for dozens of addresses. Neither fact is deep; both are the difference between a five-minute diagnosis and an evening of guessing.