Linux Networking & TCP/IP for Developers · Lesson

Bash Scripting for Networking

Write Bash scripts to automate routine network checks, configuration changes, and log analysis.

Bash Scripting for Networking is a free Linux Networking & TCP/IP for Developers lesson on CoddyKit — lesson 1 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Linux Networking & TCP/IP for Developers learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

Automate Network Tasks with Bash

Bash scripting lets you automate repetitive network tasks on Linux. Instead of typing commands manually, you can write scripts to do the work for you. This saves time and reduces errors.

We'll learn how to use Bash to check network status, configure settings, and analyze logs. It's a powerful skill for any developer working with Linux networks.

Your First Network Script

Every Bash script starts with a 'shebang' line, telling the system which interpreter to use. For Bash, it's usually #!/bin/bash. Then you add your commands. Make the script executable with chmod +x script_name.sh and run it with ./script_name.sh.

#!/bin/bash
# A simple script to check localhost reachability

echo "Checking localhost..."
ping -c 1 localhost
echo "Ping command finished."

Using Variables for Flexibility

Variables store data like IP addresses or hostnames, making your scripts more flexible. Define a variable like HOSTNAME="google.com" (no spaces around =). Access its value using a dollar sign, like $HOSTNAME.

#!/bin/bash
# Define a target host
TARGET_HOST="8.8.8.8"

echo "Pinging $TARGET_HOST..."
ping -c 2 $TARGET_HOST
echo "Done."

Passing Arguments to Scripts

You can make scripts more dynamic by passing information to them as arguments. These are accessed inside the script using $1 for the first argument, $2 for the second, and so on. $0 is the script's name.

#!/bin/bash
# Script to ping an IP provided as an argument
# Usage: ./ping_arg.sh <IP_ADDRESS>

if [ -z "$1" ]; then
  echo "Usage: $0 <IP_ADDRESS>"
  exit 1
fi

TARGET_IP="$1"
echo "Pinging $TARGET_IP with 3 packets..."
ping -c 3 $TARGET_IP

Conditional Logic: if Statements

Use if statements to make decisions in your scripts. The exit status of a command ($?) is crucial: 0 means success, non-zero means failure. You can check this status to react accordingly.

if command; then ... fi: Checks if command succeeded.
if [ condition ]; then ... fi: Checks a condition.

#!/bin/bash
# Check if a host is reachable
HOST="google.com"
ping -c 1 $HOST > /dev/null 2>&1

if [ $? -eq 0 ]; then
  echo "$HOST is reachable."
else
  echo "$HOST is NOT reachable."
fi

Looping Through Network Targets

The for loop is great for repeating commands for a list of items, like multiple IP addresses or hostnames. This is perfect for checking the status of several devices or performing actions on a range of IPs.

#!/bin/bash
# Loop through a list of hosts and ping them
HOSTS="localhost 8.8.8.8 192.168.1.254" # Replace with actual IPs/hosts

echo "Checking connectivity for multiple hosts:"
for HOST in $HOSTS; do
  echo "--- Pinging $HOST ---"
  ping -c 1 $HOST > /dev/null 2>&1
  if [ $? -eq 0 ]; then
    echo "$HOST is UP."
  else
    echo "$HOST is DOWN."
  fi
  echo "" # Add a blank line for readability
done

Managing Output with Redirection

Output redirection controls where a command's output goes. > writes to a file (overwriting it), >> appends to a file. The pipe | sends the output of one command as input to another, which is powerful for filtering and processing data.

Simple Log Analysis with Bash

Bash is excellent for quick log analysis. Tools like grep can search for patterns, and awk can process text line by line, often used for extracting specific fields. Combining these with pipes | lets you build powerful log parsers.

#!/bin/bash
# Simulate a log file
echo "INFO: User login successful for admin" > app.log
echo "ERROR: Database connection failed" >> app.log
echo "INFO: User logout for guest" >> app.log
echo "WARNING: High CPU usage detected" >> app.log
echo "ERROR: File not found: config.txt" >> app.log

echo "Searching for 'ERROR' messages in app.log:"
grep "ERROR" app.log

echo ""
echo "Extracting the error message only:"
grep "ERROR" app.log | awk -F': ' '{print $3}'
rm app.log # Clean up the temporary log file

Combined Network Status Script

Let's combine what we've learned to build a more useful script. This script will check a list of hosts, report their status, and log the results to a file. It uses variables, loops, conditionals, and output redirection.

#!/bin/bash
# Network Status Checker
# Checks a list of hosts and logs their status

LOG_FILE="network_status.log"
HOSTS="localhost 8.8.8.8 192.168.1.1" # Example hosts

echo "--- Network Status Report ($(date)) ---" > $LOG_FILE
echo "Checking the following hosts: $HOSTS" >> $LOG_FILE
echo "" >> $LOG_FILE

for HOST in $HOSTS; do
  echo "Checking $HOST..." | tee -a $LOG_FILE
  ping -c 1 -W 1 $HOST > /dev/null 2>&1
  if [ $? -eq 0 ]; then
    echo "  $HOST is UP." | tee -a $LOG_FILE
  else
    echo "  $HOST is DOWN." | tee -a $LOG_FILE
  fi
  echo "" | tee -a $LOG_FILE # Blank line for readability
done

echo "Report saved to $LOG_FILE"
cat $LOG_FILE
rm $LOG_FILE # Clean up the log file

Bash Scripting Quiz

Test your understanding of Bash scripting for networking!

Recap: Bash for Network Automation

You've learned the fundamentals of Bash scripting for network automation! We covered:

Script structure and execution.
Using variables and arguments for dynamic scripts.
Implementing conditional logic with if statements.
Automating tasks for multiple targets with for loops.
Managing command output with redirection and pipes.
Basic log analysis with grep and awk.

These skills are essential for streamlining network management and troubleshooting on Linux. Keep practicing by automating your own routine network tasks!

Frequently asked questions

Is the “Bash Scripting for Networking” lesson free?

Yes — the full text of “Bash Scripting for Networking” is free to read here on the web, and the Linux Networking & TCP/IP for Developers course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Linux Networking & TCP/IP for Developers course, upgrade to CoddyKit PRO.

What will I learn in “Bash Scripting for Networking”?

Write Bash scripts to automate routine network checks, configuration changes, and log analysis. You practise Linux Networking & TCP/IP for Developers with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Linux Networking & TCP/IP for Developers?

No prior experience is required. Linux Networking & TCP/IP for Developers on CoddyKit is structured for beginners through advanced learners; this is — lesson 1 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Bash Scripting for Networking” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Linux Networking & TCP/IP for Developers lesson?

Yes. Every Linux Networking & TCP/IP for Developers lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

← Back to Linux Networking & TCP/IP for Developers