{"id":3438,"date":"2026-10-15T14:29:49","date_gmt":"2026-10-15T06:29:49","guid":{"rendered":"http:\/\/www.egodaam.com\/blog\/?p=3438"},"modified":"2026-10-15T14:29:49","modified_gmt":"2026-10-15T06:29:49","slug":"how-to-view-network-information-in-a-terminal-486e-d10a9b","status":"publish","type":"post","link":"http:\/\/www.egodaam.com\/blog\/2026\/10\/15\/how-to-view-network-information-in-a-terminal-486e-d10a9b\/","title":{"rendered":"How to view network information in a terminal?"},"content":{"rendered":"

If you\u2019ve ever sat in front of a black terminal window, typing commands that make you feel like a software detective, you\u2019re not alone. When I started my company building rugged, reliable terminals for field technicians, network administrators, and even small business teams, I quickly learned that many people who reach out to us don\u2019t just want a device that works\u2014they want to actually understand what\u2019s happening on the network around them, without having to fire up a clunky graphical interface. That\u2019s why today, I\u2019m breaking down how to view network information right in the terminal, sharing tips I\u2019ve picked up over years of working with teams that swear by the speed and simplicity of command-line tools. Terminal<\/a><\/p>\n

<\/p>\n

Let\u2019s start with the basics. If you\u2019ve just logged into a terminal, your first move should be to figure out what network interfaces your device is using. Interfaces are the \u201cpipes\u201d your network traffic flows through\u2014think Ethernet ports, Wi-Fi adapters, or even virtual interfaces for VPNs. The go-to command here is ifconfig<\/code>, though on many modern systems, ip addr<\/code> has replaced it. Run ip addr<\/code> in your terminal, and you\u2019ll get a breakdown of every interface, including its name (like eth0<\/code> for Ethernet or wlan0<\/code> for Wi-Fi), its MAC address, and its assigned IP address. For example, if you see something like inet 192.168.1.100\/24<\/code> under wlan0<\/code>, that means your Wi-Fi adapter has an IP address of 192.168.1.100, which is the local address your router uses to talk to your device.<\/p>\n

A quick note here: some people get intimidated by the extra details ip addr<\/code> shows, like the subnet mask or broadcast address. If you just want to confirm your device is connected to the network, you can narrow it down with ip -br addr<\/code>, which gives a shorter, more readable list of interfaces and their IPs. This is especially useful if you\u2019re working on one of our terminals, which are designed to display this kind of output clearly even in bright sunlight or low light\u2014no squinting at tiny graphics needed.<\/p>\n

Once you know your interfaces, the next step is to check if your device can actually reach other networks, and where it\u2019s being routed. That\u2019s what the traceroute<\/code> command is for. If you run traceroute google.com<\/code>, it will map every hop your data takes to get from your terminal to Google\u2019s servers, showing how long each hop takes and if any are dropping packets. This is a lifesaver for troubleshooting slow or spotty connections\u2014last year, a client of ours, a small manufacturing team, was dealing with constant downtime on their shop floor terminals. They used traceroute<\/code> to find that a faulty router in the back office was adding 200ms of delay between the shop and the server room, a problem they never would have spotted by just looking at a Wi-Fi signal bar.<\/p>\n

If you don\u2019t have traceroute<\/code> (some lightweight Linux distributions leave it out by default), mtr<\/code> is a great alternative\u2014it combines the functionality of ping<\/code> and traceroute<\/code> into one real-time tool. Run mtr google.com<\/code> and you\u2019ll get a scrolling view of packet loss and latency for every hop, which makes it even easier to spot where a connection is failing.<\/p>\n

Next up, let\u2019s talk about checking which devices are on your local network. If you\u2019re setting up a new terminal for your office, or need to find a printer or server that\u2019s on the same Wi-Fi or Ethernet, arp -a<\/code> is the command you need. The Address Resolution Protocol (ARP) table maps local IP addresses to their corresponding MAC addresses, so when you run arp -a<\/code>, you\u2019ll see a list of every device on your local network, along with its hardware address. For example, if you see 192.168.1.1 - 00:1a:2b:3c:4d:5e<\/code>, that\u2019s probably your router\u2019s IP and MAC address. I\u2019ve used this countless times to track down devices that are using up IP addresses without permission, especially when we\u2019re helping clients set up multiple terminals for a single location.<\/p>\n

Another tool for scanning local networks is nmap<\/code>, which is more powerful but takes a little more practice. If you run nmap -sn 192.168.1.0\/24<\/code>, it will scan every IP in your subnet (the 192.168.1.0\/24<\/code> part) and tell you which devices are online. It doesn\u2019t just give you IPs, either\u2014it can guess the device type (like a laptop, printer, or server) and even show open ports on each device. We recommend learning the basics of nmap<\/code> for any team that uses our terminals for network setup, because it\u2019s way faster than logging into a router\u2019s web interface to check connected devices.<\/p>\n

Now, let\u2019s get into port information, which is critical if you\u2019re setting up services like a web server, a file share, or a remote desktop connection. A port is like a door on your device that lets specific types of traffic in or out. To see which ports are open and which programs are using them, two commands stand out: netstat<\/code> and ss<\/code>. ss<\/code> is the modern replacement for netstat<\/code>, so we\u2019ll focus on that. Run ss -tuln<\/code> and you\u2019ll get a list of all TCP and UDP ports that are listening for incoming connections, along with their state (like LISTEN<\/code> meaning a service is waiting for traffic) and the program that\u2019s using them. For example, if you see 0.0.0.0:22<\/code> under the LISTEN<\/code> state, that means SSH is running on your device, which is perfect for remote access to your terminal.<\/p>\n

If you want a more detailed view, including which remote devices are connected to your ports, run ss -tua<\/code>. This will show you all active TCP connections, both incoming and outgoing, along with the source and destination IPs and ports. Last month, a client reached out saying their terminals were running slow, and we used ss<\/code> to find that a malicious program had opened an outgoing connection to a foreign IP, sucking up bandwidth. That fix was a lot faster than digging through graphical network tools, all because of a simple terminal command.<\/p>\n

Let\u2019s not forget about DNS, which is what turns domain names like google.com into IP addresses your terminal can use. If you\u2019re having trouble reaching a website or a server by name, the nslookup<\/code> or dig<\/code> commands will tell you which DNS server your terminal is using and what IP it\u2019s returning for a domain. Run nslookup google.com<\/code> and you\u2019ll see your device\u2019s default DNS server (usually your router or an ISP server) and the IP addresses it\u2019s pointing to. If that IP looks wrong, or if the command times out, it means your DNS settings are off, which could be causing network issues. We\u2019ve had dozens of clients use these commands to fix problems where their terminals were set to a faulty public DNS server, and switching to their router\u2019s local DNS fixed the issue in 30 seconds.<\/p>\n

Now, let\u2019s talk about how this all ties into using our terminals. One of the biggest advantages of our devices is that they\u2019re designed for real-world use, where power might be spotty, internet connections might be unstable, and you can\u2019t always carry a laptop with you. All of the commands I\u2019ve mentioned work perfectly on our terminals, and because we use a lightweight, optimized operating system, they load fast even when you\u2019re in a field location or a remote warehouse. For example, a technician working on a construction site can grab one of our terminals, plug in an Ethernet cable, run ip addr<\/code> to confirm the interface is up, mtr site.server.local<\/code> to check if the local server is reachable, and get back to fixing the issue in minutes\u2014no need to set up a laptop or wait for a graphical interface to load.<\/p>\n

I\u2019ve also seen teams use these commands to monitor network performance over time. If you run ping 8.8.8.8 -i 1 -c 60<\/code>, it will send 60 ping packets to Google\u2019s DNS server once a second, giving you a clear picture of packet loss and latency over a minute. You can redirect that output to a file with > network_log.txt<\/code> so you can review it later, which is perfect for tracking down intermittent issues that only happen at certain times of day. Our terminals have enough storage to save these logs, so you can pull them back later to show IT teams or use them for troubleshooting future problems.<\/p>\n

One common question we get is: what if I\u2019m connecting to a secure network, or need to check for VPN connections? If you\u2019re using a VPN, the ip addr<\/code> command will show a new interface, usually named tun0<\/code> or wg0<\/code> for WireGuard, with a separate IP address for the VPN tunnel. Run ip route<\/code> to see the routing table, which will show that traffic destined for the internet goes through your regular interface, and traffic for your work network goes through the VPN interface. That\u2019s a quick way to confirm your VPN is working without having to click through a client app.<\/p>\n

Of course, no tool is perfect. For beginners, the terminal can feel overwhelming at first, with all the text and no point-and-click. That\u2019s why we build our terminals with easy access to a command cheat sheet, so new users can quickly look up the most common network commands without having to Google them in the field. We also include preconfigured scripts that automate some of these steps, like a script that runs ip addr<\/code>, mtr 192.168.1.1<\/code>, and ss -tuln<\/code> all in one go, giving you a full network status report in 10 seconds.<\/p>\n

At the end of the day, knowing how to view network information in the terminal is a skill that saves time, solves problems fast, and gives you more control over your network, no matter what device you\u2019re using. Our terminals are built to make that skill work for you, whether you\u2019re a network administrator, a field technician, or a small business owner managing a few office devices. If you\u2019re looking for a terminal that\u2019s reliable, easy to use, and built for real-world network work, we\u2019d love to talk through your needs. We can help you figure out which model works best for your team, answer any questions you have about command-line tools, and support you every step of the way as you integrate these commands into your workflow.<\/p>\n

<\/p>\n

If you\u2019re ready to learn more or discuss how our terminals can fit your network management needs, don\u2019t hesitate to reach out. We\u2019re here to help you work smarter, not harder, whether you\u2019re in the office, out in the field, or anywhere in between.<\/p>\n

Metering Junction Boxes<\/a> References<\/p>\n

    \n
  1. Linux man-pages project. ip(8) \u2013 Linux manual page.<\/li>\n
  2. Linux man-pages project. ss(8) \u2013 Linux manual page.<\/li>\n
  3. Linux man-pages project. arp(8) \u2013 Linux manual page.<\/li>\n
  4. Fyodor. Nmap Network Scanning: The Official Nmap Project Guide to Network Discovery and Security Scanning.<\/li>\n
  5. Linux man-pages project. mtr(8) \u2013 Linux manual page.<\/li>\n<\/ol>\n
    \n

    Hangzhou Lingcheng Technology Co., Ltd.<\/a><\/p>\n

    Address: Room 1613, 16th Floor, Building 3, No. 99 Wangzhou Road, Liangzhu Street, Yuhang District, Hangzhou City, Zhejiang Province
    E-mail: LCKJ0408@163.com
    WebSite:     https:\/\/www.lingchengelectric.com\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

    If you\u2019ve ever sat in front of a black terminal window, typing commands that make you … How to view network information in a terminal?<\/span>Read more<\/a><\/p>\n","protected":false},"author":436,"featured_media":3438,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[3401],"class_list":["post-3438","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-industry","tag-terminal-4380-d14c1c"],"_links":{"self":[{"href":"http:\/\/www.egodaam.com\/blog\/wp-json\/wp\/v2\/posts\/3438","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.egodaam.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.egodaam.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.egodaam.com\/blog\/wp-json\/wp\/v2\/users\/436"}],"replies":[{"embeddable":true,"href":"http:\/\/www.egodaam.com\/blog\/wp-json\/wp\/v2\/comments?post=3438"}],"version-history":[{"count":0,"href":"http:\/\/www.egodaam.com\/blog\/wp-json\/wp\/v2\/posts\/3438\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/www.egodaam.com\/blog\/wp-json\/wp\/v2\/posts\/3438"}],"wp:attachment":[{"href":"http:\/\/www.egodaam.com\/blog\/wp-json\/wp\/v2\/media?parent=3438"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.egodaam.com\/blog\/wp-json\/wp\/v2\/categories?post=3438"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.egodaam.com\/blog\/wp-json\/wp\/v2\/tags?post=3438"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}