Paths/DevOps Engineer/Networking / IP Addressing & Routes
Trace Your Network Setup
Every container and server has an IP, a route to the outside world and a way to test reachability. Find this machine's addresses and prove connectivity to the default gateway.
Validator
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- Directory ~/report exists○
- File ~/report/gateway.txt exists and contains the default gateway IP○
02Walkthrough
6 steps- 01
Show the network interfaces
ip a lists every interface. lo is the loopback (127.0.0.1 — yourself), eth0 is the real interface with this machine's IP: 172.17.0.2/16.
ip a - 02
Show the routing table
ip route shows where packets go. The 'default via' line names the gateway — the router that forwards traffic to the rest of the network. Here: 172.17.0.1.
ip route - 03
Ping the gateway
ping sends ICMP echo requests and waits for replies. 0% packet loss against the gateway proves the local network works.
ping 172.17.0.1 - 04
Ping a hostname
ping also accepts hostnames — this exercises DNS before ICMP. lab.internal resolves through /etc/hosts and DNS in this lab.
ping lab.internal - 05
Record the gateway
Write the gateway IP you found into the report file.
echo 'gateway: 172.17.0.1' > ~/report/gateway.txt - 06
Verify and submit
cat the file to confirm, then submit.
cat ~/report/gateway.txt
03Stuck?
0 of 3 revealedTake a hint without losing the lab — each one points at the thing to look at, not at the answer.
04AI Tutor
guides, never solvesTell me what you're stuck on — I'll nudge, not solve. Which requirement are you looking at?
04Notebook
saved locally in this browserlearner@lab — ubuntu:24.04
Session is disposable
↑/↓ recalls commands · Ctrl+Enter submits · type help for the command list