Daily Tech Dispatch

PC Troubleshooting

How to Check Network Interface: Cross-Platform Guide

Master network diagnostics. Learn how to check network interface status, speed, and IP details on Windows, Mac, and Linux with our 2026 guide.

"Slow internet" is a frustratingly vague complaint. You’re waiting for a file to download, or your video call is freezing, and you just know something is wrong, but where? Is it the router? The ISP? Your computer? This is where learning how to check network interface status becomes your most powerful troubleshooting tool. It cuts through the guesswork and points directly to the bottleneck.

I’ve spent the last 15 years working with everything from home users battling Wi-Fi dropouts to enterprise engineers debugging complex latency spikes. In almost every case, the answer started with the same simple question: What is my device actually seeing on that network port?

In this guide, we’re not just looking at IP addresses. We’re diving into the physical link speeds, the IP address configuration details, and the subtle signs of packet loss or driver conflicts that most "quick fix" articles ignore. Whether you’re on Windows 11, a headless Linux server, or the latest macOS Sonoma, I’ll walk you through the exact commands and GUI paths to diagnose your connectivity. No jargon without explanation, no fluff. Just the tools you need to find the truth.

Minimalist close-up of ChatGPT interface displayed on a dark monitor screen, highlighting AI technology.

What Is a Network Interface? Physical vs. Logical

To fix a network problem, you have to understand the two layers you are interacting with. When you plug in an Ethernet cable or connect to Wi-Fi, you are engaging with two distinct entities that often cause confusion.

Understanding NICs, IPs, and Subnet Masks

Think of your Network Interface Card (NIC) as the physical mail slot on your house. It’s the hardware component—whether it’s a physical chip on your motherboard or a USB adapter—that actually listens for and sends electrical or radio signals. This is the "Physical" layer. Every NIC has a permanent, factory-burned MAC address (Media Access Control). This is its hardware identity. It doesn’t change when you move to a new house or switch ISPs.

Then there is the "Logical" layer: the IP address configuration. This is the postal address. While your mail slot (NIC) stays the same, your postal address (IP) can change. This is where the subnet mask comes in. It tells your device, "Here’s the range of IPs that are on your local street."

I often see users panic when they see a different IP address after a reboot. That’s normal. In most home and office environments, we use DHCP (Dynamic Host Configuration Protocol). Your router acts as the landlord, handing out IP leases. If you look at your connection details, you’ll see "Lease Obtained" and "Lease Expires." When that timer runs out, your device automatically requests a new address. If you’re running a server or a printer that needs to be reachable at the same address always, you’d use a static IP. But for a standard workstation, DHCP is almost always the right call. Understanding the difference between the physical hardware (up/down status) and the logical assignment (IP/lease) is 50% of troubleshooting.

Close-up of a smartphone screen showing popular social media and utility app icons.

How to Check Network Interface on Windows 10/11

Windows buries its network details in a few different places, which can be confusing if you’re just looking for a quick answer. The modern UI has changed significantly with Windows 11, moving away from the legacy Control Panel, but both paths still exist.

Method 1: Using Graphical User Interface (GUI)

If you prefer clicking over typing, here is the fastest path on Windows 11. The old "Control Panel > Network and Sharing Center" route still works, but it feels clunky. The new Settings app is much more direct.

  1. Open Settings (Win + I).
  2. Navigate to Network & internet > Hardware properties.
  3. This screen lists every physical adapter on your machine. You’ll see your Wi-Fi card, your primary Ethernet port, and even virtual adapters like Hyper-V.
  4. Click on the adapter you want to inspect. Look for the Link speed (Receive/Transmit).

I always tell clients to check this "Link speed" field first. If your cable is gigabit but this says "100 Mbps," you’ve found your culprit: a bad cable, a port set to half-duplex, or a hardware limitation. For Wi-Fi, this will show you if you’re connected at 802.11ac or 802.11ax (Wi-Fi 6), which gives a rough idea of your potential max speed.

Method 2: Using Command Line (CMD & PowerShell)

For detailed diagnostics, the command line is superior. Open Command Prompt or PowerShell.

The Go-To: ipconfig /all

ipconfig /all

This command dumps everything. It’s a lot of text, but it’s invaluable. You’ll see:

  • IPv4 Address: Your current IP.
  • DHCP Enabled: If "Yes," you are relying on a router to assign addresses.
  • Default Gateway: Usually your router’s IP (e.g., 192.168.1.1).
  • MAC Address: The physical identifier of the card.

The Pro Move: PowerShell PowerShell is more structured. To check just the status and speed of your active adapters:

Get-NetAdapter | Select-Object Name, Status, LinkSpeed
  • Status: "Up" means active. "Disconnected" or "Disabled" means it’s off.
  • LinkSpeed: Shows the negotiated speed (e.g., 1 Gbps).

In my experience, Get-NetAdapter is faster to parse visually. If you see a "Down" status on your primary Ethernet card, it’s usually a physical layer issue—loose cable, dead switch port, or a crashed driver.

How to Check Network Interface on Linux

Linux is the heart of the internet, and its tools are the most powerful for checking status. However, the landscape has changed. The old ifconfig command is effectively deprecated on most modern distributions in favor of the ip command from the iproute2 suite.

Modern Command: 'ip addr' (Recommended)

On any recent Debian, Ubuntu, or RHEL-based system, use this:

ip addr

Or, for a specific interface like eth0 or wlan0:

ip addr show eth0

The output is dense but readable. Look for the flags in square brackets.

  • [UP] or [LOWER_UP]: The interface is active and the physical link is established.
  • [NO-CARRIER]: The interface is up logically, but there is no physical signal (e.g., cable unplugged or Wi-Fi not associated).

You’ll also see the inet line, which displays your IP address and the subnet mask (in CIDR notation, like 255.255.255.0 or /24). If you’re running a server, you’ll want to check if the IP was assigned via DHCP (if configured that way) or if it’s static. The ip addr command is the standard for a reason: it’s part of the core system, requires no extra installation, and provides the most accurate view of the kernel’s network stack.

Legacy Command: 'ifconfig' & Hardware Tools

You will still see ifconfig in older tutorials. It works, but it’s less detailed. For quick checks, it’s fine:

ifconfig -a

However, to check the physical link speed on Linux, you need ethtool. This is a critical tool that is often missing in basic installers.

sudo ethtool eth0

Look for Speed: 1000Mb/s or Speed: 100Mb/s. This tells you the negotiated rate with the switch. If you’re getting 100Mbps on a gigabit link, the problem is usually the cable (Cat5 vs Cat5e) or a bad port.

To verify the hardware is actually detected by the OS at the driver level, use lshw:

lshw -class network

This will list your NICs and confirm the driver in use. If your card isn’t showing up here, it’s not a configuration issue—it’s a hardware or kernel module issue.

How to Check Network Interface on macOS

Apple has kept its network tools fairly consistent, but the naming convention can be confusing for people coming from Linux (eth0) or Windows (Ethernet 0). macOS uses en0, en1, en2, etc.

GUI: System Settings & System Profiler

On macOS Ventura and later (including Sonoma), the path is:

  1. Click the Apple menu > System Settings.
  2. Go to Network.
  3. Click on the connection you are using (e.g., "Wi-Fi" or "Ethernet").
  4. Click Details....

Here, you can see the IP address, DNS servers, and the link speed (for Ethernet). For Wi-Fi, you can check the RSSI (signal strength) and channel.

For a text-based dump that is great for scripting or sharing with support, use system_profiler in the terminal:

system_profiler SPNetworkDataType

This outputs a structured text file containing details for every hardware port. It’s the closest equivalent to Windows’ ipconfig /all in terms of readability for humans.

CLI: 'ifconfig' and 'networksetup'

The ifconfig command still works well on macOS, though Apple is slowly migrating to ip in newer versions.

ifconfig -a

You’ll see en0, en1, lo0, etc. lo0 is the loopback interface (127.0.0.1), which is essential for internal services.

To figure out which en number corresponds to which physical port (a common headache), use networksetup:

networksetup -listallhardwareports

This will explicitly map "Wi-Fi" to en0 and "Thunderbolt Ethernet" to en5 (or whatever number it is on your machine). This is the definitive way to list all network interfaces on Mac OS without guessing.

Advanced: Diagnosing Errors & Monitoring Throughput

Knowing your interface is "Up" only tells you the cable is plugged in. It doesn’t tell you if data is flowing correctly. This is where we move from status checks to active diagnostics.

Using Ping & Tracert for Connectivity Checks

The most basic connectivity test is ping. But how you interpret it matters.

  • Windows: ping 8.8.8.8 (Use a public IP like Google’s DNS to bypass local DNS issues).
  • Linux/Mac: ping 8.8.8.8

If you get replies, check the RTT (Round-Trip Time). Low RTT is good. High variance in RTT indicates jitter.

  • Packet Loss: This is the red flag. 1-5% loss might be a flaky Wi-Fi signal. 10%+ loss means your connection is effectively broken.

If ping works but the internet is slow, the issue might be further down the line. Use tracert (Windows) or traceroute (Linux/Mac) to see where the hop is failing.

traceroute 8.8.8.8

Look for where the * * * (timeout) appears. If it’s at the first hop, it’s your router or ISP. If it’s at hop 10, it’s an upstream provider issue. Note: Some networks block traceroute, so a timeout doesn’t always mean a broken link, but it’s a strong indicator.

Real-Time Throughput & Health Monitoring

Static checks are good, but real-time monitoring reveals the truth about saturation.

  • Linux: iftop or nload are fantastic. They show you exactly how much bandwidth is being used by which process. If your interface is hitting 95% of its capacity, you have saturation.
  • macOS/Windows: Task Manager (Windows) or Activity Monitor (Mac) have network graphs, but they are often laggy. For a quick check, netstat -i (Linux/Mac) shows interface statistics, including collisions and drops.

High error rates or collision counts on an Ethernet port usually point to a physical layer issue—bad cable, electrical interference, or a duplex mismatch. In my experience, 80% of "mystery" speed issues on wired networks turn out to be a cable that works for basic pings but can’t sustain gigabit throughput due to internal breakage.

Unique Insight: Automated Checks via Python & PowerShell

If you’re managing a home server or a CI/CD pipeline, running ipconfig manually is not scalable. I recommend building small scripts to automate these checks. This allows you to log network health over time or trigger alerts when an interface goes down.

Scripting Your Network Checks

Python (Cross-Platform) Using the psutil library is the easiest way to get structured data.

import psutil

def check_network_interface():
    addrs = psutil.net_if_addrs()
    stats = psutil.net_if_stats()
    
    for iface_name, iface_addr in addrs.items():
        # Skip loopback
        if iface_name == 'lo' or iface_name == 'lo0':
            continue
            
        # Get IP
        ip = next((i.address for i in iface_addr if i.family == 2), None) # 2 is IPv4
        # Get Status
        status = stats[iface_name].isup
        speed = stats[iface_name].speed # May be 0 if unsupported
        
        print(f"Interface: {iface_name}, IP: {ip}, Up: {status}, Speed: {speed}Mbps")

check_network_interface()

This snippet is great for monitoring. You can wrap it in a cron job and email yourself if isup returns False.

PowerShell (Windows) For Windows environments, a one-liner can export the status of all adapters to a CSV for logging.

Get-NetAdapter | Select-Object Name, Status, LinkSpeed, MacAddress | Export-Csv -Path "C:\logs\net_status_$(Get-Date -Format 'yyyyMMdd').csv"

Run this every 5 minutes via Task Scheduler, and you’ll have a historical record of your network health. When a connection drops, you can look back and see exactly when the Status changed to Disconnected. This level of network interface status command automation is what separates a reactive user from a proactive one.

FAQ

What command do I use to check network interfaces in Linux? The modern standard is ip addr. It provides detailed information about IP addresses, MAC addresses, and link status. ifconfig is a legacy tool that still works on many systems but lacks some features of ip. For checking specific link speeds and driver information, use ethtool <interface_name>.

How do I check if my network interface is up or down? In the command line, look for the UP flag in the output of ip addr. In the Windows GUI, a green dot next to the network icon in the system tray indicates "Up." A red X or yellow triangle indicates "Down" or "Connected, no Internet." For a precise physical link status on Linux, ethtool will explicitly state "Link detected: yes" or "no."

Why is my network interface showing as disabled? Common causes include a physical cable being unplugged, the adapter being manually disabled in OS settings (Device Manager on Windows, Network settings on Mac), or a crashed driver. In many cases, simply toggling the adapter off and on again resolves driver glitches. Check your firewall rules as well; a misconfigured firewall can sometimes block the interface from communicating, though it rarely changes the "Up/Down" status itself.

How can I see the speed of my current network connection?

  • Windows: Use Get-NetAdapter in PowerShell or check the "Properties" of your connection in Settings.
  • Linux: Use ethtool eth0 (replace eth0 with your actual interface name) to see the negotiated link speed.
  • macOS: Use system_profiler SPNetworkDataType in the terminal, or check the details in System Settings > Network.

Conclusion

Troubleshooting network issues doesn’t have to be a black art. Whether you’re using ipconfig on Windows, ip addr on Linux, or ifconfig on macOS, the core goal is the same: verify the physical link status and the logical IP configuration.

I strongly recommend keeping a quick mental map of which command does what. For a quick status check, ip commands are superior. For detailed IP and DHCP lease information, ipconfig /all or ifconfig is hard to beat. And when things feel "weird," don’t skip the ethtool or netstat diagnostics to check for hardware-level errors like collisions and drops.

If you’ve followed these steps and your interface shows as "Up" with the correct IP, but you still have no internet, the problem is almost certainly external to your device. At that point, reset your router or contact your ISP. But for 90% of the issues I’ve seen over the years, the answer was found right here in the local interface settings.

Want to keep this reference handy? I’ve compiled a one-page PDF cheat sheet covering all the commands in this article. [Download the Network Check Cheat Sheet here] and subscribe for more advanced networking tutorials to keep your systems running smoothly.

Back to Home