Decoding the Alphabet Soup: A Guide to macOS Network Interface Naming

By Manny Fernandez

March 21, 2026

Decoding the Alphabet Soup: A Guide to macOS Network Interface Naming

This blog post explores the logic behind how macOS names its network interfaces, how it has changed over the years, and how you can take control of it using the command line. I did a similar post about Netplan on Linux interface naming if you want to check that out. If you’ve ever typed ifconfig into a Mac Terminal, you’ve likely been greeted by a wall of text featuring names like en0, lo0, and the mysterious awdl0. Unlike Linux, which often uses descriptive names like eth0 or wlan0 (or the newer predictable naming like enp3s0), macOS follows a convention rooted deeply in its Unix heritage.

The Historical Roots: From NeXTSTEP to Tahoe

macOS is built on Darwin, which is a hybrid of the Mach microkernel and the FreeBSD operating system. Darwin is the basis for macOS, watchOS, iOS, & tvOS. Because of this, macOS inherits the BSD style of interface naming.

The “en” Legacy – In the early days of networking, en stood for Standard Ethernet. On the original Macintosh computers with built-in Ethernet, en0 was always the physical RJ45 port.
The Wi-Fi Takeover – As Apple moved toward a wireless-first world, the naming convention stayed, but the hardware shifted. On modern MacBooks that lack a built-in Ethernet port, en0 is almost always the Wi-Fi card.
The Expansion: With the introduction of Thunderbolt and USB-C, additional physical interfaces are simply incremented: en1, en2, etc., regardless of whether they are a Thunderbolt-to-Ethernet adapter or a virtual interface.

Common Interface Types You’ll See

Beyond the standard Ethernet/Wi-Fi (enX), here is what the others actually do:

Name	Type	Description
`lo0`	Loopback	The internal “localhost” (127.0.0.1). Used for local testing.
`awdl0`	Apple Wireless Direct Link	Used for AirDrop, AirPlay, and Sidecar.
`utunX`	User Tunnel	Typically created by VPN clients (like WireGuard or Tailscale).
`bridge0`	Bridge	A virtual switch, often used for Thunderbolt Bridge or VM networking.
`p2p0`	Peer-to-Peer	Historically used for Wi-Fi Direct features.

Nuances & “Gotchas”

Order Matters – macOS assigns en numbers based on the order the drivers are initialized during boot. If you use a lot of external dongles, en3 today might be en4 tomorrow if you plug them in differently.
Service Order vs. BSD Name – In System Settings > Network, you can change the “Service Order” (which interface the Mac prefers for internet). However, changing this does not rename the interface in ifconfig. en0 remains en0 even if it’s at the bottom of the priority list.
The “Phantom” Interfaces – You might see dozens of utun or anpi interfaces. These are often internal Apple protocols (like Apple Network Protocol Interface) used for communication between the CPU and the Secure Enclave or the Liquid Glass UI components.

Command Line Tools to Check Your Setup

Don’t rely solely on ifconfig; macOS has specialized tools that provide “friendly” names.

networksetup -listallhardwareports: This is the best way to map a BSD name (like en0) to its physical hardware (like “Wi-Fi”).
scutil --nwi: Shows the “Network Information” and tells you which interface is currently the “primary” one being used for the default gateway.
ifconfig -v en0: Provides a more verbose output for a specific interface, including its status and supported media types.

I use TextExpander which allows you to enter an abreviated command and it expands it into something more useful. So if I go to my command line, and type ; and getip It runs

ifconfig | grep inet

Decoding the Alphabet Soup: A Guide to macOS Network Interface Naming

The Historical Roots: From NeXTSTEP to Tahoe

Common Interface Types You’ll See

Nuances & “Gotchas”

Command Line Tools to Check Your Setup

Recent posts