IPv4 Configuration with nmcli
Half of one objective. RHEL 10 has no ifcfg files at all, so nmcli or a keyfile is the only way. Two things are worth practising: con mod edits the profile and changes nothing live until con up, and +ipv4.addresses appends where plain ipv4.addresses replaces the whole list.
Basic Networking Guide 48 of 67 Intermediate
- OSRHEL 10.0
- Kernel6.12.0-55.9.1.el10_0
- dnf4.20.0
- Flatpak1.16.0
- TimeAbout 15 min
RHEL 10 removed /etc/sysconfig/network-scripts and the NetworkManager-initscripts-updown package with it. Connections live in /etc/NetworkManager/system-connections/*.nmconnection. Any instruction to edit ifcfg-eth0 is impossible to follow on this release - see guide 3.
| 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 for half of one objective. This matters because modifying a connection changes the stored profile rather than the running interface - so nothing happens at all until you bring it up again.
- reading what is configured right now
- creating a connection
- modifying it, and finding out why nothing happened
- using the plus and minus forms to add and remove values
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.
-
What is configured now
-
Creating a connection
-
Modifying, and why nothing happened
-
Plus and minus