How to Manage Preferred Wi-Fi Networks and Hardware Service Order Using networksetup in macOS Terminal

Configuring and managing network adapters across macOS workstations often presents subtle operational challenges. When a MacBook is docked at an office workstation connected to a gigabit Ethernet cable, macOS may stubbornly continue routing primary outbound traffic over a slower Wi-Fi connection if hardware network service priority is misconfigured. Similarly, when roaming across corporate campuses featuring overlapping SSIDs (such as an encrypted enterprise network alongside a guest portal), a Mac may auto-associate with an unoptimised network. While macOS System Settings exposes basic networking controls, advanced configuration—including modifying preferred Wi-Fi network priority, binding interfaces, and automating network deployment scripts—is best accomplished via networksetup. Mastering this native command-line utility provides complete administrative control over the macOS networking stack.

Understanding networksetup and System Configuration Framework

The networksetup binary (located at /usr/sbin/networksetup) acts as the primary administrative bridge to Apple’s System Configuration framework and the /Library/Preferences/SystemConfiguration/preferences.plist database. Unlike generic Unix tools such as ifconfig or ip, which interact with network interfaces only at the transient kernel level without persisting across reboots, networksetup writes persistent hardware configurations recognized by the macOS operating system.

Through networksetup, administrators manage three core architectural layers:

• Network Service Order: The hierarchical priority list determining which physical or virtual adapter (Thunderbolt Ethernet, Wi-Fi, USB LAN, or VPN) handles default routing.
• Preferred Wireless Networks: The ordered association table governing which SSIDs the wireless radio attempts to authenticate with when multiple networks are in range.
• Hardware Interface Bindings: The physical mapping between BSD interface identifiers (such as en0, en1, or en5) and user-facing service names.

Identifying Hardware Network Services and BSD Port Mappings

Before issuing configuration commands, you must identify how macOS maps user-friendly service names to underlying hardware interfaces.

1. Launch Terminal from /Applications/Utilities/.
2. List all detected hardware network interfaces:

   networksetup -listallhardwareports

3. Inspect the output. Notice the pairing between Hardware Port (e.g. Wi-Fi or Thunderbolt Ethernet) and Device (e.g. en0 or en1). On Apple Silicon laptops, en0 is typically Wi-Fi, whereas on desktop Macs (such as the Mac Studio), en0 is built-in Ethernet.
4. To view all active user-space network services, run:

   networksetup -listallnetworkservices

Managing Hardware Service Order and Routing Precedence

To ensure macOS automatically prioritises high-speed wired connections over wireless networks whenever an Ethernet cable is plugged in, adjust the global service order.

1. View your workstation’s current service priority list:

   networksetup -listnetworkserviceorder

   macOS lists services numbered sequentially starting from (1). The top-ranked service receives primary default gateway precedence for outbound traffic.

2. To elevate wired connections above Wi-Fi, invoke the -ordernetworkservices command followed by the exact service names in your desired priority sequence:

   sudo networksetup -ordernetworkservices "Thunderbolt Ethernet" "USB 10/100/1000 LAN" "Wi-Fi" "iPhone USB"

3. Verify the updated configuration by re-running networksetup -listnetworkserviceorder. Outbound traffic will now automatically traverse the high-speed Ethernet bus whenever connected, gracefully failing over to Wi-Fi only when undocked.

Auditing and Listing Preferred Wi-Fi Networks

Over months of travel and office moves, a Mac accumulates dozens of obsolete coffee shop, airport, and hotel Wi-Fi networks. These clutter the preference store and cause unwanted connection attempts.

1. Identify your Wi-Fi interface device name from the earlier hardware port check (e.g. en0).
2. Query the list of all remembered wireless networks:

   networksetup -listpreferredwirelessnetworks en0

3. macOS returns an ordered list of stored SSIDs. During network scanning, your Mac evaluates candidate networks in the exact sequence displayed.

Adding, Removing, and Reordering Preferred Wireless Networks

Administrators can manipulate preferred network entries to ensure corporate SSIDs take precedence over auxiliary guest portals.

Adding a Trusted Wi-Fi Network with Explicit Security Specifications

To add a secure enterprise network to your preferred association table:

sudo networksetup -addpreferredwirelessnetworkatindex en0 "Corporate-Secure" 0 WPA2E

In this command:

• 0: Represents the priority index. Setting 0 places the network at the very top of the preferred list.
• WPA2E: Specifies the security suite (accepted options include OPEN, WPA, WPA2, WPA3, WPA2E, or WPA3E).

Removing an Obsolete or Untrusted Wireless Network

To purge an insecure or obsolete network from your remembered list completely:

sudo networksetup -removepreferredwirelessnetwork en0 "Public-Airport-Guest"

Automating Interface Power and Hardware Reset via Terminal

When Wi-Fi associations hang or network interfaces fail to negotiate DHCP leases post-wake, scripting a complete hardware interface power cycle clears transient network daemon locks.

1. Turn the Wi-Fi radio off:

   networksetup -setairportpower en0 off

2. Pause for two seconds to allow the CoreWLAN subsystem to tear down active radio connections:

   sleep 2

3. Turn the Wi-Fi radio back on:

   networksetup -setairportpower en0 on

Leveraging networksetup within administrative workflows and deployment scripts provides deterministic control over network priorities, eliminates connection routing bottlenecks, and ensures enterprise macOS fleets adhere to strict connectivity governance.