Hands-on Lab·LPIC-2
An NFS export, proved from two clients
Objective 209.1 is NFS. This guide exports one directory to one host, mounts it from that host and reads a file over the network, then tries the same mount from a machine that is not in the export list. It also shows the client mounting read-write and still being unable to write, which is where the access control actually lives.
202: File Sharing Guide 19 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 NFS objective. This matters because a share can be mounted read-write and still refuse the write - the contradiction that shows where access is really decided.
- setting up a server, and one directory to share
- writing the export line, and running the reload it needs
- mounting it, and reading a file over the network
- mounting read-write, and watching the write fail anyway
- trying the same mount from a host the export does not name
Before you start
- what-stands-between-a-service-and-its-client
-
A server, and one directory to share
-
The export line, and who it names
-
Mounting it, and reading a file over the network
-
Mounted read-write, and the write still fails
-
A host that is not in the export list