Skip to content
Author Nejat Hakan
eMail nejat.hakan@outlook.de
PayPal Me https://paypal.me/nejathakan


Linux Networking Basics - Getting Connected

Introduction

Welcome to the world of Linux networking! In today's interconnected world, understanding how computers talk to each other is fundamental. Linux, being the backbone of the internet (powering countless servers, cloud instances, and embedded devices), offers powerful tools to manage network connections.

This first chapter is designed for absolute beginners. We assume you might know how to open a terminal, but perhaps terms like "IP address" or "DNS" sound a bit mysterious. Don't worry! We will break down the essential concepts piece by piece, explaining not just what they are, but why they matter. We'll learn how to check your system's network configuration and test basic connectivity using standard Linux command-line tools. Our goal is to give you the confidence to understand and interact with the most basic network settings on your Linux machine.

In this chapter, we will cover:

  1. Core Networking Concepts: IP Addresses (IPv4 & IPv6), Subnet Masks, Gateways, DNS.
  2. Essential Command-Line Tools: ip, ping, hostname.
  3. Viewing Network Configuration: Checking your IP address, MAC address, and interface status.
  4. Basic Connectivity Testing: Ensuring you can reach other devices on your network and the internet.

Let's begin by demystifying the language of networks.

Prerequisites:

  • A Linux system (physical install or a virtual machine).
  • Access to the command line (Terminal).
  • User account (root or sudo access might be needed for changing settings, but viewing often works without it).

1. Core Networking Concepts: The Language of Networks

Before we touch the keyboard, let's understand the fundamental building blocks that allow devices to communicate.

  • IP Address (Internet Protocol Address): The Unique Identifier

    • What is it? Think of an IP address like a unique postal address for your computer on a network. Just as your home address allows mail to find you, an IP address allows data packets to find your computer.
    • Why is it important? Every device that wants to communicate on an IP-based network (like your home network or the internet) needs a unique IP address within that network. Without it, other devices wouldn't know where to send information.
    • Two Versions:
      • IPv4: The older, more common format. It looks like four sets of numbers separated by dots (e.g., 192.168.1.100). Each number ranges from 0 to 255. While widely used, the world is running out of unique IPv4 addresses.
      • IPv6: The newer format, designed to solve the address shortage. It uses eight groups of four hexadecimal characters separated by colons (e.g., 2001:0db8:85a3:0000:0000:8a2e:0370:7334). It looks more complex, but provides an unimaginably vast number of addresses. Most modern systems support both.
    • Public vs. Private:
      • Public IP: An address assigned by your Internet Service Provider (ISP). This is the address your entire home network uses to talk to the wider internet. It's globally unique.
      • Private IP: Addresses used within your local network (home, office). Ranges like 192.168.x.x, 10.x.x.x, and 172.16.x.x to 172.31.x.x are reserved for private use. Your laptop might have 192.168.1.100, your phone 192.168.1.101, etc. These are not unique globally, only within your local network. Your router handles the translation between private and public IPs (this is called NAT - Network Address Translation).

  • Subnet Mask: Defining the Neighborhood

    • What is it? A subnet mask works together with an IP address. It defines which part of the IP address represents the network itself (the "street") and which part represents the specific device (the "house number") on that network.
    • Why is it important? It allows a device to quickly determine if another IP address is on the same local network or on a different, remote network. If it's local, the device can send data directly. If it's remote, it needs to send the data to the gateway (see next point).
    • How it looks (IPv4): It often looks similar to an IP address (e.g., 255.255.255.0). Another way to represent it is using CIDR (Classless Inter-Domain Routing) notation, which appends a / followed by a number to the IP address (e.g., 192.168.1.100/24). The /24 means the first 24 bits of the address define the network, and the remaining bits (32 total bits in IPv4) define the host. /24 is equivalent to 255.255.255.0.

  • Gateway (Default Gateway): The Exit Door

    • What is it? The gateway is the IP address of a router on your local network. This router acts as the "exit door" for any traffic destined for outside your local network (e.g., the internet or another office network).
    • Why is it important? When your computer wants to send data to an IP address that the subnet mask indicates is not on the local network, it doesn't send it directly. Instead, it sends the packet to the gateway's IP address. The gateway router then takes responsibility for forwarding the packet towards its final destination.
    • Common Example: In a typical home network, the gateway IP address is usually the private IP address of your Wi-Fi router (e.g., 192.168.1.1 or 192.168.0.1).

  • DNS (Domain Name System): The Internet's Phonebook

    • What is it? Humans prefer memorable names like www.google.com or www.wikipedia.org. Computers, however, communicate using numerical IP addresses. DNS is the system that translates human-readable domain names into computer-readable IP addresses.
    • Why is it important? Without DNS, you'd have to memorize the IP address for every website you want to visit! When you type www.google.com in your browser, your computer first asks a DNS server (whose IP address it knows) "What's the IP address for www.google.com?". The DNS server replies with the IP address, and then your browser can connect to Google's servers.
    • Configuration: Your computer needs to know the IP address(es) of one or more DNS servers to use. These are often provided automatically by your network (via DHCP, which we'll touch on later) or can be set manually. Common public DNS servers include Google's (8.8.8.8, 8.8.4.4) and Cloudflare's (1.1.1.1, 1.0.0.1).

2. Essential Command-Line Tools

Linux provides powerful command-line utilities to view and manage network settings. We'll start with the most fundamental ones.

  • ip command: The Modern Multi-tool

    • What is it? The ip command is part of the iproute2 package and is the standard, modern tool for viewing and manipulating routing, network devices, interfaces, and tunnels in Linux. It replaces older, now deprecated commands like ifconfig and route.
    • Why use it? It's powerful, versatile, and the current standard. Learning ip is essential for modern Linux network administration.
    • Common Subcommands: We'll focus on a few key ones initially:
      • ip address (or ip addr, ip a): Shows information about network interfaces, their IP addresses, and MAC addresses.
      • ip link: Shows information about the network interfaces themselves (the hardware/virtual device level), like their state (UP/DOWN) and MAC address.
      • ip route: Shows the kernel's IP routing table (how your system decides where to send network traffic).

  • ping: Testing Reachability

    • What is it? ping sends a small network packet (called an ICMP Echo Request) to a target host (specified by IP address or hostname). If the target host is reachable and configured to respond, it sends back an ICMP Echo Reply.
    • Why use it? It's the most basic way to check if your computer can "talk" to another device on the network or the internet. It measures the round-trip time for the packets and indicates if any packets were lost.
    • Basic Usage: ping <target_ip_or_hostname> (e.g., ping 192.168.1.1, ping www.google.com). Press Ctrl+C to stop it.

  • hostname: Identifying Your Machine

    • What is it? This simple command displays or sets the system's hostname. The hostname is a human-friendly label for your computer on the network (e.g., my-laptop, webserver-01).
    • Why use it? Helps identify your machine, especially when managing multiple systems. It's also often part of the command prompt, reminding you which machine you're logged into.
    • Basic Usage: hostname (displays the current hostname).

3. Viewing Network Configuration

Let's use the ip command to see how your system is configured. Open your terminal.

  • Listing Network Interfaces and IP Addresses: 

    ip address show
# Or the shorter versions:
# ip addr show
# ip a

    • Explanation of Output: You'll likely see output for at least two interfaces:
      • lo (Loopback Interface): This is a special virtual interface that the computer uses to talk to itself. It almost always has the IPv4 address 127.0.0.1 and the IPv6 address ::1. It's essential for many applications. Look for inet 127.0.0.1/8 and inet6 ::1/128. The /8 and /128 are the subnet masks in CIDR notation for the loopback addresses.
      • One or more Physical/Virtual Interfaces: These represent your actual network connection(s). Names vary, but common ones include:
        • eth0, eth1, ... : Typically wired Ethernet connections.
        • wlan0, wlan1, ... : Typically wireless (Wi-Fi) connections.
        • enpXsY, ensX: Newer "predictable network interface names" based on hardware location/MAC address (e.g., enp0s3).
      • Key Information for Each Interface:
        • <state UP> or <state DOWN>: Indicates if the interface is currently active or inactive. UP is needed for communication.
        • link/ether xx:xx:xx:xx:xx:xx: This is the MAC Address (Media Access Control address). It's a globally unique hardware identifier burned into the network card by the manufacturer. It operates at a lower level (Layer 2) than IP addresses (Layer 3).
        • inet Y.Y.Y.Y/ZZ: Your IPv4 address (Y.Y.Y.Y) and subnet mask (/ZZ in CIDR). This is crucial! scope global usually means it's a regular address usable on the network. scope link might indicate an address only valid on the local link.
        • inet6 A:B:C:D:E:F:G:H/XXX: Your IPv6 address and prefix length. scope global means it's a globally routable address. scope link indicates a link-local address (used only on the immediate network segment, often starts with fe80::).

  • Viewing Link Layer Information: 

    ip link show

    • Explanation: This focuses on the interface itself, not the IP addresses. You'll see the interface names, their state (UP/DOWN), MAC address (link/ether), and other details like MTU (Maximum Transmission Unit - the largest packet size allowed).

  • Viewing the Routing Table: 

    ip route show
# Or:
# ip route

    • Explanation: This shows how your Linux system decides where to send packets. Key entries include:
      • default via G.G.G.G dev interface_name: This is your default gateway. G.G.G.G is the IP address of your router. Any traffic not matching other specific routes will be sent via this gateway using the specified interface_name. This is essential for reaching the internet.
      • N.N.N.0/MM dev interface_name proto kernel scope link src Y.Y.Y.Y: This indicates that the network N.N.N.0/MM (your local network, derived from your IP and subnet mask) is directly reachable (scope link) out of the specified interface_name. src Y.Y.Y.Y shows the source IP your system will use when sending packets to this network.

  • Viewing DNS Server Information: DNS server configuration is typically stored in the /etc/resolv.conf file. 

    cat /etc/resolv.conf

    • Explanation: Look for lines starting with nameserver. The IP address following nameserver is the address of a DNS server your system will query. You might see multiple nameserver lines for redundancy. You might also see a search line, which specifies domain suffixes to try automatically if you type a short hostname.
    • Important Note: On modern systems using tools like systemd-resolved or NetworkManager, /etc/resolv.conf might be automatically generated or be a symbolic link. The actual configuration might reside elsewhere, but this file usually reflects the currently used servers.

4. Basic Connectivity Testing

Now that you can see your configuration, let's test if it works using ping.

  • Test 1: Ping the Loopback Interface: 

    ping -c 4 127.0.0.1

    • Explanation: -c 4 tells ping to send only 4 packets instead of running continuously. 127.0.0.1 is the loopback address. This test checks if your system's internal networking stack is functioning correctly. It should always work if your system is running properly. You should see 4 replies with very low time values (e.g., < 0.1 ms).

  • Test 2: Ping Your Own IP Address: Find your main interface's IPv4 address using ip a (e.g., 192.168.1.100). 

    ping -c 4 <your_ip_address>
# Example: ping -c 4 192.168.1.100

    • Explanation: This checks if the network interface itself is responding at the IP level. This should also work if the interface is UP and has an IP assigned.

  • Test 3: Ping Your Default Gateway: Find your default gateway address using ip route (e.g., 192.168.1.1). 

    ping -c 4 <your_gateway_ip>
# Example: ping -c 4 192.168.1.1

    • Explanation: This tests connectivity to your local router. If this works, it means you can reach other devices on your immediate local network. The time values might be slightly higher (e.g., 1-10 ms).

  • Test 4: Ping a Public Internet Address (by IP): Let's ping one of Google's public DNS servers. 

    ping -c 4 8.8.8.8

    • Explanation: If this works, it confirms:
      • Your gateway is working and forwarding traffic correctly.
      • Your ISP connection is active.
      • You can reach the wider internet (at least this specific server).
    • The time values will depend on your internet connection quality (e.g., 10-100 ms or more).

  • Test 5: Ping a Public Internet Hostname: This tests DNS resolution and internet connectivity. 

    ping -c 4 www.google.com

    • Explanation: If this works, it means:
      • Your DNS servers (from /etc/resolv.conf) are reachable and working, correctly translating www.google.com to an IP address.
      • You can then reach that IP address via your gateway and ISP.
    • Troubleshooting: If ping 8.8.8.8 worked but ping www.google.com fails (e.g., "Temporary failure in name resolution" or "unknown host"), it strongly suggests a DNS problem. Check your /etc/resolv.conf file and try pinging the DNS server IPs listed there.

Conclusion

You've taken your first steps into Linux networking! We've demystified core concepts like IP addresses, subnet masks, gateways, and DNS. You've learned how to use the fundamental ip, ping, and hostname commands to inspect your system's network configuration and perform basic connectivity tests. Understanding these basics is crucial before moving on to more complex topics. In the next chapter, we'll explore how to make network configurations persistent and look at common network services and troubleshooting tools.

Now, let's put this knowledge into practice with a hands-on workshop.

Workshop: Exploring Your Network Configuration

Goal:

To practice using basic Linux commands (ip, ping, hostname, cat) to identify your machine's network settings and test its connectivity. This workshop requires no configuration changes, only observation and testing.

Scenario:

You are sitting at your Linux machine (or connected to it) and need to document its basic network identity and verify it can communicate locally and with the internet.

Prerequisites:

  • A Linux system with a working network connection (wired or wireless).
  • Access to the command line terminal.

Steps:

1. Identify Your Hostname:

What is your computer called on the network?

hostname
  • Explanation: This command simply prints the configured hostname of your Linux system. Note down the output.

2. List Network Interfaces and Find Your Primary Interface:

Let's see all network adapters recognized by the system.

ip link show
  • Explanation: This command lists all network interfaces (link layer devices). Look for the interface that corresponds to your main connection (e.g., eth0, enp0s3 for wired; wlan0 for wireless). Note its name and whether its state includes UP. Also, find its link/ether address – this is the MAC address. Note it down.

3. Find Your IP Address and Subnet Mask:

Now let's find the IP address assigned to your primary interface.

ip address show
# Or focus on the specific interface you identified in step 2:
# ip address show dev <interface_name>
# Example: ip address show dev enp0s3
  • Explanation: Scan the output for the interface name you noted in Step 2. Find the line starting with inet (for IPv4) that has scope global. Note down the IP address and the CIDR notation (e.g., 192.168.1.55/24). If you see an inet6 address with scope global, note that down too (this is your global IPv6 address, if you have one).

4. Identify Your Default Gateway:

Where does your system send traffic destined for the internet?

ip route show
  • Explanation: Look for the line starting with default via. The IP address listed immediately after via is your default gateway. Note down this IP address. Also, note the interface name mentioned on that line (dev <interface_name>) - it should match your primary interface from Step 2.

5. Identify Your DNS Servers:

Which servers does your system ask to translate domain names?

cat /etc/resolv.conf
  • Explanation: Look for lines beginning with nameserver. Note down the IP address(es) listed on these lines. These are your currently configured DNS servers.

6. Test Internal Network Stack:

Can your system talk to itself?

ping -c 3 127.0.0.1
  • Explanation: We send 3 packets (-c 3) to the loopback address. Verify that you receive 3 replies (0% packet loss) and the time is very short. This confirms the basic TCP/IP stack is working.

7. Test Local Network Connectivity:

Can you reach your router (gateway)? Use the gateway IP you found in Step 4.

ping -c 3 <your_gateway_ip>
# Example: ping -c 3 192.168.1.1
  • Explanation: We send 3 packets to the gateway. Verify you get replies (0% packet loss). This confirms you can communicate on your local network segment. Note the approximate round-trip time.

8. Test Internet Connectivity (by IP):

Can you reach a known server on the internet directly by its IP?

ping -c 3 8.8.8.8
  • Explanation: We ping Google's public DNS server. Verify you get replies. This confirms your gateway is routing traffic correctly to the internet. Note the approximate round-trip time – it will likely be higher than pinging your gateway.

9. Test DNS Resolution and Internet Connectivity:

Can your system resolve a domain name and reach the resulting server?

ping -c 3 www.debian.org
  • Explanation: We ping a well-known hostname. First, your system uses DNS (servers from Step 5) to find the IP for www.debian.org. Then, it sends ping packets to that IP. Verify you get replies. If this works, it confirms both DNS resolution and internet connectivity are functional.

Workshop Summary Sheet (Fill this in as you go):

  • Hostname: _____________________________
  • Primary Interface Name: _____________________
  • MAC Address: ___________________________
  • IPv4 Address / Subnet (CIDR): ____________ / ___
  • IPv6 Address (Global, if any): __________________
  • Default Gateway IP: _______________________
  • DNS Server IP(s): ______________, ______________
  • Ping 127.0.0.1 Successful? (Yes/No) Time: \~ ___ ms
  • Ping Gateway Successful? (Yes/No) Time: \~ ___ ms
  • Ping 8.8.8.8 Successful? (Yes/No) Time: \~ ___ ms
  • Ping www.debian.org Successful? (Yes/No) Time: \~ ___ ms

Workshop Conclusion:

You have successfully used standard Linux commands to inspect your network configuration and verify connectivity at different levels – from the local machine to the local network and out to the public internet. You've also confirmed that DNS resolution is working. Having this baseline information is the first step in any network management or troubleshooting task.