Capstone labs · Lesson 6 of 18 · 8 minutes

Capstone network audit

Review address, route, firewall, and SSH client config.

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 address
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 firewall
Run ufw status verbose.
Hint & worked example
Inspect or adjust the training firewall rule list. No real firewall changes occur.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
ufw status verbose
```
Remember: Firewall rules should be scoped and reviewed; simulator access is not a production change approval.
4
Resolve SSH config
Run ssh -G lab.
Hint & worked example
Inspect a fixed SSH training scenario; no real remote connection is made.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
ssh -G lab
```
Remember: Verify host identity and choose credentials deliberately on real systems.

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.
ufw: Inspect or adjust the training firewall rule list. No real firewall changes occur.
Firewall rules should be scoped and reviewed; simulator access is not a production change approval.
ssh: Inspect a fixed SSH training scenario; no real remote connection is made.
Verify host identity and choose credentials deliberately on real systems.

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.

$ ufw status verbose

Status: active
Logging: on (simulated)
Default: deny incoming, allow outgoing
- allow 22/tcp
- allow 80/tcp
- allow 443/tcp
- deny 23/tcp

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

$ ssh -G lab

host lab
user learner
hostname clairos-learn-lab
identityfile ~/.ssh/training_key
pubkeyauthentication yes
passwordauthentication no

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 “Capstone network audit”, which interpretation is safe?A successful first check guarantees that every dependent service is healthy.An interface address, a route, and a reachable service are separate parts of connectivity.A command appearing in history proves it completed successfully.

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Capstone package audit 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