>
Every Linux machine is a node on a network, and the fastest way to understand it is from the command line. This track teaches you to read interfaces and IP addresses, list open ports and live sockets, prove reachability with ping, resolve names through DNS, and reach remote hosts over SSH — so you can see exactly what your box is talking to, and what's talking back.
Verified on Ubuntu 24.04 and Debian 12. Dedicated networking walkthroughs are on the way — meanwhile, these fundamentals give you the terminal habits every network task depends on.
Networking lives in the terminal — this guide builds the navigation, piping and permission skills every ip, ss and ssh command relies on.
USB Wi-Fi dongles and Ethernet adapters show up here first. The same enumeration mindset — query the system, read the tree — carries straight into network debugging.
read the guide →We're writing focused, tested guides on reading IP addresses with ip, checking open ports with ss, ping and traceroute diagnostics, DNS lookups with dig and resolvectl, and working over SSH. New networking tutorials land on Linuxier regularly — check back or follow the blog for the next drop.
ip a and ip route to read addresses, links and the routing table — the map of how packets leave your box.ss -tulpn, tie ports to processes, and spot anything bound to the outside world.ping, trace the path, and resolve names with dig so you know it's not a DNS problem.Start local: know your own address and routes. Then look outward: which ports are open, whether a remote host answers, and how names resolve to numbers. SSH ties it all together by letting you run these same checks on a machine across the room — or across the world.
Networking sits right next to Security — an open port is only safe if you meant to open it — and feeds directly into DevOps, where services bind ports and pipelines reach remote hosts. New to the terminal? Start with Linux Basics.