Networking · Lesson 1 of 26 · 8 minutes

IP address review

Inspect interface addresses and routes.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Show addresses
Run ip addr.
Hint & worked example
Inspect simulated interface and route state.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
ip addr
```
Remember: An interface address, a route, and a reachable service are separate parts of connectivity.
2
Show route
Run ip route.
Hint & worked example
Inspect simulated interface and route state.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
ip route
```
Remember: An interface address, a route, and a reachable service are separate parts of connectivity.
3
Show host
Run hostname.
Hint & worked example
Read the simulated host name.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
hostname
```
Remember: A name helps orient an operator but is not proof of network reachability.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

ip: Inspect simulated interface and route state.
An interface address, a route, and a reachable service are separate parts of connectivity.
hostname: Read the simulated host name.
A name helps orient an operator but is not proof of network reachability.

Worked example and expected result

$ ip addr

1: lo: <LOOPBACK,UP> mtu 65536
    inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,UP> mtu 1500
    inet 10.20.30.40/24 scope global eth0

Exit status: 0. The command completed successfully in the training fixture.

$ ip route

default via 10.20.30.1 dev eth0 proto static
10.20.30.0/24 dev eth0 proto kernel scope link src 10.20.30.40

Exit status: 0. The command completed successfully in the training fixture.

$ hostname

clairos-learn-lab

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Repeat this workflow in the sandbox with a different scratch filename. Keep the system fixtures unchanged and compare the observed output with your expectation before moving on.

Explain it

In “IP address review”, which interpretation is safe?An interface address, a route, and a reachable service are separate parts of connectivity.A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.

Apply it elsewhere

Before adapting the ip workflow from “IP address review” to another server, what should you do?Paste the training paths unchanged into production.Skip output inspection whenever the command is familiar.Confirm the current directory, target identity, permissions, and the installed command behavior first.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Socket listening review Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

GNU Coreutils manual · GNU Bash manual