OS Mastery Simple OS learning for a global audience Start Here

LAB-NET-02 - Ping and Reachability

Use ping to test reachability in a more structured way, separating local stack checks, gateway checks, and broader connectivity checks.

NET Networking and Communication

Ping and Reachability

Use ping to test reachability in a more structured way, separating local stack checks, gateway checks, and broader connectivity checks.

15 min BEGINNER LINUX
Before this lab
Lab LAB-NET-01 - Interfaces and IP Addresses
What success looks like
  • Use ping to test reachability in a more structured way, separating local stack checks, gateway checks, and broader connectivity checks.
  • Repeat the workflow without copy-paste or step-by-step prompting.
Safety notes
  • Run network changes in a lab or VM first so you do not break your active connection unexpectedly.

Part A: The Field Guide

ping is useful, but only when you are clear about what it is actually testing.

It is best treated as a reachability probe, not a total network verdict.

Key Limitation

A host or firewall may ignore ICMP ping even when the service you care about is healthy. So a failed ping is useful evidence, but not final proof by itself.

Part B: The Drill Deck

Terminal required: use short, bounded tests.

G
Guided Step by step - type exactly this and compare the result
>

Exercise G1: Test loopback

  1. Run ping -c 2 127.0.0.1
  2. Confirm that the local stack responds
  3. Explain why this still does not prove outside connectivity

Exercise G2: Test broader reachability

  1. Run ping -c 2 8.8.8.8
  2. Note whether packets return and what the latency roughly looks like
  3. Explain how this differs from the loopback test

Exercise G3: Compare IP versus hostname

  1. Run ping -c 1 8.8.8.8
  2. Run ping -c 1 google.com
  3. Explain why the second test depends on one extra layer
S
Solo Task described, hints available - figure it out
>

Exercise S1: Gateway reasoning

If you know your default gateway, test it with a short ping and explain why this sits between loopback testing and outside-internet testing in the troubleshooting order.

Exercise S2: Bound the command

Explain why ping -c 3 target is often better for a quick check than an endless ping session.

M
Mission Real scenario - no hints, combine multiple skills
>

Mission M1: Write the three-step reachability ladder

Write a short sequence using ping that checks:

  1. local loopback
  2. local network path or gateway
  3. outside reachability

If you can explain what each step proves, the lab is doing the right job.

What to do next

Best next step Learning

Return to the related lesson if you want the concept explained more deeply.

Open now
Troubleshooting

Use problem-first help when this lab maps to a real issue.

Open now Reference

Look up commands, topics, and tasks while you practice.

Open now