Networking and Remote Commands

# CHAPTER 14

Networking and Remote Commands #

1. Introduction #

2. Learning Objectives #

• Write an automated ICMP ping sweep script to verify host connectivity.

• Extract and evaluate HTTP status codes (e.g., 200 OK) using curl.

• Download external dependencies autonomously utilizing wget or curl.

• Execute administrative commands on remote servers utilizing ssh.

• Transfer files securely between servers utilizing scp.

• Enforce strict timeouts on network commands to prevent script hanging.

3. Layer 3 Automation (The Ping Sweep) #

*Important:* In a script, you must use -c 1 to limit the ping to a single pulse, and you must use -W 1 (or -t 1 depending on the OS) to limit the timeout to 1 second. If a server is completely offline, you don't want the script pausing for 10 seconds waiting for a response!

#!/bin/sh

# Define the cluster nodes
NODES="192.168.1.10 192.168.1.11 192.168.1.12"

echo "Initiating ICMP Ping Sweep..."

for IP in $NODES; do
    # Ping once (-c 1), Timeout fast, suppress output
    ping -c 1 -W 1 "$IP" > /dev/null 2>&1
    
    # Check the exit code!
    if [ $? -eq 0 ]; then
        echo "[ONLINE] Node $IP is responding."
    else
        echo "[OFFLINE] Node $IP is DOWN!"
    fi
done

4. Layer 7 Automation (HTTP API Checks) #

#!/bin/sh

URL="https://example.com/api/health"

# -s (Silent), -o /dev/null (Discard the actual HTML page data)
# -w "%{http_code}" (Write out ONLY the 3-digit HTTP response code)
STATUS=$(curl -s -o /dev/null -w "%{http_code}" "$URL")

if [ "$STATUS" = "200" ]; then
    echo "API is Healthy (HTTP 200)."
else
    echo "API Failure! Returned HTTP Code: $STATUS"
fi

*(This 10-line script replaces thousands of dollars of commercial website monitoring software).*

5. Remote Administration (ssh and scp) #

1. Remote Command Execution:

#!/bin/sh
TARGET="admin@10.0.0.50"

echo "Checking disk space on remote server..."
# Pass the 'df -h' command to SSH
ssh "$TARGET" 'df -h /'

2. Automated Secure File Transfer (scp): If you generate a backup archive locally, you can push it to a remote storage server securely.

#!/bin/sh
# Copy backup.tar to the /archives folder on the remote server
scp /tmp/backup.tar admin@10.0.0.60:/archives/

6. Diagrams/Visual Suggestions #

• Top layer (Widest): Ping (Layer 3). "Is the machine turned on?"

• Bottom layer (Narrowest): Curl (Layer 7). "Is the web application actually returning healthy HTML data?"

7. Best Practices #

• Implement Strict Timeouts: Network commands are historically dangerous in scripts because they "hang." If a script runs curl http://offline-server.com without a timeout flag, the script will literally freeze in the terminal for 2 minutes waiting for the network request to naturally drop. Always enforce timeouts (curl --max-time 5, ping -W 1) to ensure scripts fail rapidly and continue execution.

8. Common Mistakes #

• Grepping for Ping output: Beginners often try to run ping and pipe the output into grep to look for the phrase "bytes from" to determine if it succeeded. This is incredibly inefficient and error-prone depending on the operating system's exact ping string format. Always rely on the $? exit status code (0 for success, 1 for failure) which is universally standardized across all Unix distributions.

9. Mini Project: Remote Health Dashboard #

1. 1. nano cluster_health.sh

1. 2. Write the code:

#!/bin/sh

# List of remote nodes (Assuming SSH keys are configured)
NODES="node1.corp.com node2.corp.com node3.corp.com"

echo "=== CLUSTER HEALTH DASHBOARD ==="

for SERVER in $NODES; do
    echo "Querying $SERVER..."
    
    # Use SSH with an explicit timeout to prevent hanging on a dead node
    LOAD=$(ssh -o ConnectTimeout=3 "$SERVER" 'uptime' 2>/dev/null)
    
    if [ $? -eq 0 ]; then
        echo "[OK] $SERVER | $LOAD"
    else
        echo "[FATAL] $SERVER is unreachable or SSH timed out!"
    fi
done

1. 3. Run it. You now have a centralized dashboard gathering live telemetry from an entire cloud fleet.

10. Practice Exercises #

1. 1. Explain the operational difference between monitoring a web server via ping versus curl. Which tool would successfully detect if a web application developer accidentally broke the website's code resulting in a 500 Internal Server Error?

1. 2. Why is it an absolute architectural requirement to include a timeout flag (e.g., --max-time 5) when writing automated curl scripts?

11. MCQs with Answers #

12. Interview Questions #

• Q: A developer complains that their automated deployment script freezes for exactly two minutes before reporting an error when attempting to download an asset via curl from a broken URL. Explain the mechanical networking behavior causing this freeze, and provide the exact flag required to enforce a "Fail Fast" methodology in the script.

• Q: You are tasked with writing a shell script to monitor a critical REST API. Walk me through the logical progression of troubleshooting steps your script should execute, starting from Layer 3 (Network) and ending at Layer 7 (Application).

• Q: Explain why a systems engineer should never parse the literal text output of the ping command using grep to determine success within a shell script, and describe the mathematically superior alternative.

13. FAQs #

14. Summary #

15. Next Chapter Recommendation #