Networking · Lesson 2 of 26 · 8 minutes

Socket listening review

Read listener state with ss.

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 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.
2
Search config listeners
Run grep listen /etc/nginx/sites-available/learn.conf.
Hint & worked example
Select input lines that match a pattern; -i ignores case, -n adds line numbers, and -v inverts selection.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
grep listen /etc/nginx/sites-available/learn.conf
```
Remember: No matches is exit status 1, which is different from a malformed invocation.
3
Compare firewall
Run ufw status.
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
```
Remember: Firewall rules should be scoped and reviewed; simulator access is not a production change approval.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

ss: Inspect simulated listening sockets and connection information.
A listening socket is not proof of correct application responses or external reachability.
grep: Select input lines that match a pattern; -i ignores case, -n adds line numbers, and -v inverts selection.
No matches is exit status 1, which is different from a malformed invocation.
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.

Worked example and expected result

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

$ grep listen /etc/nginx/sites-available/learn.conf

  listen 443 ssl;

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

$ ufw status

Status: active
- allow 22/tcp
- allow 80/tcp
- allow 443/tcp
- deny 23/tcp

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 “Socket listening review”, which interpretation is safe?No matches is exit status 1, which is different from a malformed invocation.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 grep workflow from “Socket listening 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: Lsof network 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