Hands-on Lab·LPIC-2
Apache on Debian and RPM families
Topic 208 is web services, and this guide installs Apache on both families to show how much differs around identical software: one distribution starts it and the other does not, the configuration lives in different directories, and only one of them is reachable from the client until a firewall rule is added.
202: HTTP Services Guide 12 of 29 Intermediate
- PlatformsUbuntu 26.04 LTS + AlmaLinux 10.2
- Block devicesone 50 GB disk
- TimeAbout 22 min
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| LPIC2-A01 | 192.168.0.78 | Ubuntu 26.04 LTS | Primary service host - BIND, Apache, Samba, Postfix. Topic 204 RAID runs on loop devices; this machine has no spare disk | 2 Core | 4 GB | 50 GB |
| LPIC2-B01 | 192.168.0.79 | AlmaLinux 10.2 | Second service host - nginx, NFS, DNS secondary, and the other family's spelling of each service | 2 Core | 4 GB | 50 GB |
| LPIC2-C01 | 192.168.0.80 | Ubuntu 26.04 LTS | Client - resolves, mounts and connects, so every service is proven from a machine that is not running it | 2 Core | 4 GB | 50 GB |
This guide includes
Use this for the web services topic on either family. This matters because both servers work locally and only one answers the client - the firewall is the difference, and nothing in the service says so.
- installing the same software, and finding that one family starts it for you
- sharing the one path they agree on, and differing on several they do not
- asking from the client, and getting an answer from only one server
- opening the firewall, and watching the same request succeed
- reading what the server recorded, for both requests
Before you start
- what-stands-between-a-service-and-its-client
-
Same software, different starting behaviour
-
The same document root, different everything else
-
The client asks, and only one server answers
-
The firewall was the difference
-
What the server recorded