Connecting to Wi-Fi via Terminal on macOS: A Professional Approach

Using a graphical interface to connect to a wireless network seems like the most obvious and straightforward solution for most macOS users. However, system administrators, developers, and advanced users often encounter situations where the standard menu is unavailable, frozen, or requires automation. In such cases, Command line, providing direct access to network management system services.

The terminal not only allows you to establish a basic connection, but also perform in-depth diagnostics, clear cached DNS data, or force a switch to another access point, ignoring the default network priority. networksetup and other utilities gives you full control over your network adapter MacBook or iMac.

In this article, we'll take a detailed look at connecting to Wi-Fi using console commands exclusively, covering common errors and troubleshooting methods. You'll learn how to manage connections like engineers, bypassing the limitations of the graphical interface.

Checking the network interface status

Before attempting to establish a connection, you need to make sure that the operating system correctly detects your wireless adapter and that it is active. In macOS, network interfaces are often named something like en0, en1 or awdl0, and it is important not to confuse the physical Wi-Fi module with virtual interfaces.

To obtain a list of all available services and their statuses, use the utility networksetupThis command will display a complete list of configurations, where you should look for an entry containing the word "Wi-Fi" or "AirPort." This identifier will be used in all subsequent commands to manage the connection.

networksetup -listallnetworkservices

If you see your interface in the list, but it's marked as disabled, you need to enable it. It often happens that after system crashes, the software Wi-Fi switch remains in the "Off" position, and no connection attempts will be successful without first enabling it through the console.

Please note that in newer versions of macOS, interface names may differ from the classic ones. Use the command ifconfig For a more detailed view of the technical specifications and link status, this will help you determine whether the device driver is running at a low level.

Search for available wireless networks

After confirming the presence of an interface, the next logical step is to scan the surrounding airwaves. The terminal provides a list of available access points, including their names (SSIDs), signal strengths, and the channels they operate on. This is especially useful in office buildings, where many networks have similar names.

The command used for scanning is airport, which is located along the path /System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airportTo avoid typing the full path each time, it's convenient to create a symbolic link or use the full path directly. The result will be a table with technical data.

/System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport -s

In the output, you'll see the SSID, BSSID (router MAC address), RSSI (signal strength), CHANNEL, and HT (high-speed mode) columns. Pay attention to the values. RSSI: The closer it is to 0 (for example, -40 is better than -80), the more stable the connection will be. Negative values ​​closer to zero indicate a stronger signal.

Sometimes the list may display hidden networks that don't broadcast their names. In this case, the SSID column will display a blank field or special characters. To connect to these networks, you'll need to know the exact network name in advance, as the terminal won't be able to guess it automatically.

Wi-Fi network connection algorithm

The connection process itself requires precise command syntax. You must specify the service name (obtained in the first step), the network name (SSID), and the password.

The basic command looks like this: networksetup -setairportnetworkIt takes three arguments: the service name, the network name, and the password. If the network name or password contains spaces, they must be enclosed in quotation marks, otherwise the terminal will interpret the command incorrectly.

networksetup -setairportnetwork "Wi-Fi" "MyHomeNetwork" "SuperSecretPassword123"

Executing this command initiates the association process with the access point. The system will attempt to authenticate and obtain an IP address via DHCP. A success or error message may appear in the logs, but the terminal itself often returns silently if no obvious errors occur.

It's worth noting that when connecting via Terminal, macOS may request permission to use access keys in the keychain. If you're working in unattended mode, make sure your user has write access to the system keychain; otherwise, the process may freeze while waiting for input.

Diagnostics and obtaining an IP address

After successfully executing the connection command, don't start working immediately. You need to make sure that your computer has actually been assigned an IP address and routes have been configured. The absence of an address in the format 169.254.x.x indicates a problem with the router's DHCP server.

To check the current status, use the command ipconfig getifaddr, specifying the name of your interface (usually en0). If you receive an empty string or an address in the 169.254 range in response, it means you're connected to the router, but it's not providing an address. Resetting leases can help in this case.

ipconfig getifaddr en0

It's also helpful to check DNS resolving. Even if you have an IP address, the internet may not work due to incorrect DNS settings. Use the utility scutil or just try pinging an external resource, for example, ping 8.8.8.8If you can ping but can't access websites, the problem is with your DNS.

If you see that the IP address is assigned correctly, but you still can't access the internet, the blocking may be occurring at the firewall or proxy server level. Check your proxy settings in the section networksetup -getwebproxy "Wi-Fi"to eliminate the presence of unnecessary configurations.

Managing saved networks and priorities

macOS maintains a list of known networks and attempts to connect to them automatically based on priority. Sometimes the system "locks onto" a weak network in the next room, ignoring the strong signal from your home router. You can use the terminal to flexibly manage this list, deleting unnecessary ones and changing the priority order.

To remove a specific network from memory, use the command networksetup -removenetworkThis is useful if you've changed your router password, but your Mac keeps trying to connect with the old password, causing authorization errors. Clearing the list often resolves issues with a "hanging" connection status.

networksetup -removenetwork "Wi-Fi" "Old_Office_Network"

You can also change the network preference order so that critical connections are always at the top. networksetup -setnetworkserviceorder Allows you to reorder services, but requires care in numbering. An error in ordering may cause Ethernet to stop prioritizing Wi-Fi.

⚠️ Note: Deleting networks via the terminal permanently removes them from the list of known networks. If you plan to connect to this access point again, you will need to re-enter the password.

In corporate environments, SSID hiding or MAC address filtering is often used. In such cases, simply deleting the network may not help, requiring manual configuration with the security type (WPA2 Enterprise, etc.), which requires more complex command parameters.

Resetting network settings and troubleshooting

When standard methods fail, a radical yet effective solution remains: a complete network reset. This will reset all Wi-Fi, Ethernet, and Bluetooth configurations to factory defaults, deleting all saved passwords and DNS settings.

In modern versions of macOS (Big Sur, Monterey, Ventura, and newer), a convenient reset option has appeared through the menu, but through the terminal, this can be done forcibly by deleting the preference files. However, Deleting files /Library/Preferences/SystemConfiguration/com.apple.airport.preferences.plist requires superuser rights and a reboot.

A safer method for resetting via CLI is to power cycle the interface and clear the cache. Commands networksetup -setairportpower Allows software to emulate pressing the Wi-Fi switch. This often "shakes" the driver and clears frozen states.

sudo networksetup -setairportpower "Wi-Fi" off
sudo networksetup -setairportpower "Wi-Fi" on

If this does not help, check whether the connection is blocked by antivirus software or configuration profiles (MDM) installed by the organization. Command profiles list will show active profiles that may override your manual network settings.

⚠️ Note: Interfaces and commands may vary slightly depending on the macOS version. Always check the official Apple Developer documentation for the most up-to-date syntax for your OS version, as Apple periodically changes the structure of its networking frameworks.

Please note that persistent connection problems may indicate a physical fault with the antenna or Wi-Fi module, especially if the terminal does not detect the adapter at all or returns I/O errors when attempting to scan.

Secret command for detailed logging

Use the log stream --predicate 'subsystem == "com.apple.network"' --style syslog command to view network activity in real time. This will help you see exactly where the connection is being disconnected.

Frequently Asked Questions (FAQ)

Why does the networksetup command say the service cannot be found?

You're most likely using the wrong service name. On macOS, names are case-sensitive and space-sensitive. Run networksetup -listallnetworkservices and copy the name exactly as it appears in the list, including any spaces at the end.

Is it possible to connect to a hidden network (Hidden SSID) via terminal?

Yes, team -setairportnetwork It also works for hidden networks. The key is to know the exact network name (SSID) and security type. If the network is hidden, it won't appear in the list during scanning, but connecting using the exact name is possible.

How do I save my password in my keychain when connecting via CLI?

By default, macOS attempts to save the password in Keychain Access. If the prompt doesn't appear, make sure your account has permission to modify the "login" keychain. Sometimes you need to manually enter the password once through the graphical interface so the system remembers it for future CLI commands.

What to do if the IP address starts with 169.254?

This is an APIPA address, which is assigned automatically when the device cannot obtain an address from the DHCP server. Check the cable (if it's Ethernet), reboot the router, or try manually entering a static IP via networksetup -setmanual, if you know the correct subnet.