Hands-on Lab·Red Hat Certified System Administrator
Network Services at Boot
One objective, and it is a two-part answer that a one-part answer fails: NetworkManager must be enabled, and the connection must be set to autoconnect. Either one alone gives a machine with no network after a reboot.
Basic Networking Guide 52 of 67 Beginner
- OSRHEL 10.0
- Kernel6.12.0-55.9.1.el10_0
- dnf4.20.0
- Flatpak1.16.0
- TimeAbout 9 min
connection.autoconnect defaults to yes and is not written into the keyfile when it holds the default - so its absence from the file means yes, not no. nmcli -f NAME,AUTOCONNECT con show is the reliable way to read it.
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| RHCSA-A01 | 192.168.0.31 | RHEL 10.0 | Practice node (graded) - spare /dev/sda | 2 Core | 4 GB | 50 GB + 15 GB |
This guide includes
Use this because a one-part answer fails this objective. This matters because the connection has to autoconnect AND the service has to be enabled - satisfying one without the other looks correct and is not.
- setting the connection half, with autoconnect
- setting the service half, with the unit enabled
- seeing why answering only one of the two fails the objective
Before you start
- A sudo-capable account.
- Every address change on this page is made on a dummy interface, not on the machine's real one. Reconfiguring the interface you are connected through is the one operation here that cannot be undone remotely.
-
The connection half
-
The service half