For anyone managing a server or troubleshooting a network, the command line for IP address information is an indispensable tool. While graphical interfaces exist, the terminal provides a direct, scriptable, and universally available method to inspect network configuration. This approach delivers details that are often hidden from standard system preferences, allowing for a deeper understanding of how your machine connects to the wider internet and local networks.
Identifying Your Primary Address
The most common task is to simply view the active IP address assigned to your machine. The specific command varies slightly depending on the operating system, but the principle remains the same: query the network interface table.
Linux and macOS: Using ip and ifconfig
On modern Linux distributions, the ip command is the standard. Running ip addr show or the shorthand ip a lists all interfaces and their associated addresses. You will see entries for lo (loopback) and your primary Ethernet or wireless adapter, typically named eth0 , ens33 , or wlan0 . The inet field next to your active connection displays the IPv4 address in standard dotted-decimal notation.
Alternatively, the ifconfig command, though deprecated on many systems, still provides a human-readable snapshot. If available, typing ifconfig without arguments usually displays the configuration for all interfaces, including the netmask and broadcast address.
Windows: Leveraging ipconfig
Windows users rely on the ipconfig command, which is designed specifically for network diagnostics. Opening Command Prompt or PowerShell and typing ipconfig will list the IPv4 Address for each active adapter. Look for the section labeled "Ethernet adapter" or "Wireless LAN adapter" to find the relevant information. For a more detailed view that includes the MAC address, you can use ipconfig /all .
Targeting Specific Interfaces
Servers often have multiple network interfaces, such as a public NIC for internet traffic and a private NIC for internal communication. In these scenarios, filtering the output is necessary to avoid confusion.
Filtering by Interface Name
Determining Public vs. Private Addressing
Understanding the difference between a public IP address and a private IP address is critical for network troubleshooting. The command line usually reveals both, but interpreting them correctly requires context.
Private Network Details
The address retrieved from ip addr or ipconfig is almost always a private, or RFC 1918, address. These ranges—such as 192.168.x.x, 10.x.x.x, and 172.16.x.x to 172.31.x.x—are used internally within a home or office network. Your router uses Network Address Translation (NAT) to manage traffic between these private addresses and the single public address assigned by your Internet Service Provider (ISP).
