Server operations · Lesson 5 of 36 · 7 minutes

Host network view

Inspect simulated hostname, addresses, and listening sockets.

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
Read hostname
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.
2
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.
3
Show listeners
Run ss -tulpn.
Hint & worked example
Inspect simulated listening sockets and connection information.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
ss -tulpn
```
Remember: A listening socket is not proof of correct application responses or external reachability.

Understand the pattern

Server operators need to know what is listening before changing firewall rules.

hostname: Read the simulated host name.
A name helps orient an operator but is not proof of network reachability.
ip: Inspect simulated interface and route state.
An interface address, a route, and a reachable service are separate parts of connectivity.
ss: Inspect simulated listening sockets and connection information.
A listening socket is not proof of correct application responses or external reachability.

Worked example and expected result

$ hostname

clairos-learn-lab

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

$ 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.

$ ss -tulpn

Netid State  Local Address:Port  Process
udp   UNCONN 0.0.0.0:68          lab-dhcp
tcp   LISTEN 0.0.0.0:22          sshd
tcp   LISTEN 0.0.0.0:80          nginx
tcp   LISTEN 0.0.0.0:443         nginx

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 “Host network view”, 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 “Host network view” 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: Service list 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