Why Network monitoring script in Bash Scripting? - Purpose & Use Cases

The Big Idea

What if your network could tell you it's sick before you even notice?

The Scenario

Imagine you are responsible for keeping your office internet running smoothly. Every hour, you open a web page or ping a server manually to check if the network is up. You write down the results on paper or in a text file.

The Problem

This manual checking is slow and boring. You might forget to check on time or make mistakes writing down results. If the network goes down at night or when you are away, you won't know until someone complains.

The Solution

A network monitoring script automatically checks your network at set times. It records results, alerts you if something is wrong, and runs quietly in the background. This saves you time and catches problems early.

Before vs After

✗ Before

ping -c 4 192.168.1.1
# Manually check and note results

✓ After

while true; do ping -c 1 192.168.1.1 > /dev/null && echo "Up" || echo "Down"; sleep 3600; done

What It Enables

It enables continuous, hands-free network health checks that catch issues before they become big problems.

Real Life Example

A small business uses a network monitoring script to get instant alerts when their internet connection drops, so they can call their provider quickly and avoid losing customers.

Key Takeaways

Manual network checks are slow and unreliable.

Scripts automate checks and alert you instantly.

This keeps your network stable and your work stress-free.

Practice

1. What is the main purpose of a network monitoring script using ping?

easy

A. To increase the speed of the network

B. To install software on remote devices

C. To change the IP addresses of devices

D. To check if devices on the network are reachable

Solution

1. Step 1: Understand the role of ping

   ping sends a small message to a device to see if it replies, showing if it is reachable.

2. Step 2: Identify the script's goal

   The script uses ping to detect if devices respond, helping find network problems early.

3. Final Answer:

   To check if devices on the network are reachable -> Option D

4. Quick Check:

   Ping checks reachability = B [OK]

Hint: Ping tests if a device replies to confirm reachability [OK]

Common Mistakes:

• Confusing ping with speed testing
• Thinking ping changes device settings
• Assuming ping installs software

2. Which of the following is the correct syntax to ping a device once in a bash script?

easy

A. ping /c 1 192.168.1.1

B. ping -n 1 192.168.1.1

C. ping -c 1 192.168.1.1

D. ping 192.168.1.1 -count 1

Solution

1. Step 1: Recall the ping option for count

   In Linux bash, -c specifies the number of ping requests to send.

2. Step 2: Verify the correct command format

   ping -c 1 192.168.1.1 sends exactly one ping to the IP address.

3. Final Answer:

   ping -c 1 192.168.1.1 -> Option C

4. Quick Check:

   Use -c for count in ping = D [OK]

Hint: Use -c to specify ping count in bash [OK]

Common Mistakes:

• Using Windows ping options like -n in bash
• Incorrect option syntax like /c or -count
• Omitting the count option for single ping

3. What will be the output of this script snippet?

if ping -c 1 8.8.8.8 > /dev/null; then
  echo "Host is reachable"
else
  echo "Host is unreachable"
fi

medium

A. Host is reachable

B. Syntax error

C. Host is unreachable

D. No output

Solution

1. Step 1: Understand the ping command behavior

   The command ping -c 1 8.8.8.8 sends one ping to Google's DNS server, which is usually reachable.

2. Step 2: Analyze the if condition and output

   If ping succeeds, the script prints "Host is reachable"; otherwise, it prints "Host is unreachable".

3. Final Answer:

   Host is reachable -> Option A

4. Quick Check:

   Successful ping prints reachable = C [OK]

Hint: Ping 8.8.8.8 usually succeeds, so output is reachable [OK]

Common Mistakes:

• Assuming ping always fails
• Confusing output redirection with errors
• Missing that output is suppressed with > /dev/null

4. Identify the error in this script snippet for monitoring a device:

for ip in 192.168.1.1 192.168.1.2
 do
  ping -c 1 $ip
  if [ $? -eq 0 ]; then
    echo "$ip is up"
  else
    echo "$ip is down"
  fi

medium

A. Incorrect ping option '-c'

B. Missing 'done' to close the for loop

C. Wrong variable name for IP address

D. No error, script is correct

Solution

1. Step 1: Check for loop syntax completeness

   The for loop starts with for ip in ... but lacks the closing done keyword.

2. Step 2: Confirm other parts are correct

   The ping command and if condition use correct syntax and variable names.

3. Final Answer:

   Missing 'done' to close the for loop -> Option B

4. Quick Check:

   For loops need 'done' to end = A [OK]

Hint: Always end bash loops with 'done' [OK]

Common Mistakes:

• Forgetting 'done' after loops
• Using wrong ping options
• Using undefined variables

5. You want to create a script that checks multiple IPs and logs only unreachable ones to a file named unreachable.log. Which snippet correctly does this?

hard

A. for ip in 192.168.1.1 192.168.1.2; do
ping -c 1 $ip > /dev/null || echo "$ip unreachable" >> unreachable.log
done

B. for ip in 192.168.1.1 192.168.1.2; do
if ping -c 1 $ip > /dev/null; then
echo "$ip unreachable" >> unreachable.log
fi
done

C. for ip in 192.168.1.1 192.168.1.2; do
ping -c 1 $ip >> unreachable.log
done

D. for ip in 192.168.1.1 192.168.1.2; do
ping -c 1 $ip || echo "$ip reachable" >> unreachable.log
done

Solution

1. Step 1: Understand the goal

   The script should log only unreachable IPs to unreachable.log.

2. Step 2: Analyze each option

   for ip in 192.168.1.1 192.168.1.2; do ping -c 1 $ip > /dev/null || echo "$ip unreachable" >> unreachable.log done uses ping -c 1 $ip > /dev/null || echo "$ip unreachable" >> unreachable.log, which logs IPs only if ping fails (unreachable). for ip in 192.168.1.1 192.168.1.2; do if ping -c 1 $ip > /dev/null; then echo "$ip unreachable" >> unreachable.log fi done logs reachable IPs incorrectly. for ip in 192.168.1.1 192.168.1.2; do ping -c 1 $ip >> unreachable.log done logs all ping output, not just unreachable. for ip in 192.168.1.1 192.168.1.2; do ping -c 1 $ip || echo "$ip reachable" >> unreachable.log done logs reachable IPs as unreachable.

3. Final Answer:

   for ip in 192.168.1.1 192.168.1.2; do ping -c 1 $ip > /dev/null || echo "$ip unreachable" >> unreachable.log done -> Option A

4. Quick Check:

   Use '||' to log failures only = A [OK]

Hint: Use '||' to log only when ping fails [OK]

Common Mistakes:

• Logging reachable IPs instead of unreachable
• Appending all ping output to log
• Using wrong conditional logic