-
Bug
-
Resolution: Done
-
Minor
-
RH124 - RHEL9.0-en-2-20220609
-
en-US (English)
URL:
Reporter RHNID:
Section: 5 -
Language: en-US (English)|
Workaround:
Description: The paragraph on top of the below command is packed with details for which there is no explanation. Nothing in the command explicitly pertains to DHCP or autoconnect or IPv6 listening on the local link, so this is probably something that needs further explanation. I understand that since there are no IP addresses specified, that DHCP is implied, but that might not be clear to others. Without resorting to a Google search or diving into the RHEL documentation, I don’t see how a person new to RHEL would be able to make all these leaps in thought.
The paragraph in question is ch12s05 "Configure Networking from the Command Line", header "Add a Network Connection":
| The following example adds a connection for the eno2 interface called eno2. The network information for the connection uses a DHCP service and has the device autoconnect on startup. The system also obtains IPv6 networking settings by listening for router advertisements on the local link. The configuration file name contains the value of the nmcli command con- name parameter, which is eno2. The value of the con-name parameter is saved to the /etc/ NetworkManager/system-connections/eno2.nmconnection file. |
