Traditionally, early kernel versions assigned names to network interface devices by assigning a prefix, which is typically based on the device driver, and a number, such as eth0. With the availability of different types of devices, this naming schema is no longer efficient. The names don't necessarily correspond to the chassis labels and the names themselves might be inconsistent across existing network interfaces. The inconsistency would affect embedded adapters on the system, including add-in adapters. Server platforms with several network adapters could have problems managing these interfaces.

Oracle Linux implements a consistent naming scheme for all network interfaces through the udev device manager. The scheme offers the following advantages:

• The names of the devices are predictable.

• Device names persist across system reboots or after changes are made to the hardware.

• Defective hardware can easily be identified and thus replaced.

The feature that implements consistent naming on devices is enabled in Oracle Linux by default. Network interface names are based on information that's derived from the system BIOS. Alternatively, they can be based on a device's firmware, system path, or MAC address.

Network interfaces are identified by a name that combines a prefix and a suffix. The prefix depends on the type of network interface:

• Ethernet network interfaces: en

• Wireless local area network (LAN) interfaces: wl

• Wireless wide area network (WAN) interfaces: ww

The suffix contains any of the following information:

• An on-board index number on , and thus, eno0 .

• A hot-plug slot index number sn , and thus, ens1.

  This naming schema can also include ffunction and ddevice-id that are added to the suffix.

• The bus and slot number pbussn , and thus. enp0s8.

  This naming schema can also include ffunction and ddevice-id that are added to the suffix.

• The MAC address xMAC-addr , and thus, enx0217b08b.

  Note that this naming format isn't used by Oracle Linux by default. However, administrators can implement it as an option.

1. If not already installed, install the nm-connection-editor package.

   sudo dnf install -y nm-connection-editor

2. Start the editor:

   sudo nm-connection-editor

   The editor detects the network devices that are on the system and lists them and their current states:

   Figure 1-1 Network Connections

   
   
   

3. To add or remove a connection, use the plus (+) or minus (-) buttons at the bottom of the editor window.

   If you add a connection, a window that prompts you for the connection type opens. Select a type, such as Ethernet, from the drop down list, then click Create. The Interface Editor window opens.

   Note:

   The same window opens if you edit an existing connection.

   Figure 1-2 Interface Editor

   
   
   

4. Click each tab as needed and enter the required information about the interface.

5. Click Save after you have completed the configuration.

   You must specify all the required information. Otherwise, the settings can't be saved and the editor's background terminal window would display messages that indicate the errors.

1. If not already installed, install the NetworkManager-tui package.

   sudo dnf install -y NetworkManager-tui

2. Open NetworkManager's text-based user interface.

   sudo nmtui

   Figure 1-3 TUI Main Menu

   
   
   

   To navigate the tool, use the up and down arrow keys, then press Enter to make a selection

3. To add a connection, select Edit a connection, then click Add.

4. After selecting a connection type, the Edit Connection window opens.

   Figure 1-4 Edit Connection

   
   
   

5. As an option, specify a preferred profile name and the name of the device.

6. By default, IPv4 and IPv6 configurations are set to Automatic. To change the setting, select the Automatic field and press Enter. From the drop down list, select the type of IP configuration that you want to implement, such as Manual. Then, select the corresponding Show field.

   The fields that are displayed depend on the type of IP configuration that's selected. For example, to manually configure an IP address, selecting Show displays an address field, where you would enter an IP addresses for the interface, as the following figure illustrates.

   Figure 1-5 Adding IP Addresses

   
   
   

7. Navigate through all the fields on the screen to ensure that the required information is specified.

8. After you have edited the connection, select OK.

To illustrate the different uses of the nmcli command, this procedure describes an example of adding and configuring a new Ethernet connection for the enp0s2 device. For more information about the command, see the nmcli(1) manual page.

1. (Optional): Display the network devices on the system.

   sudo nmcli device status

   DEVICE  TYPE      STATE          CONNECTION
   enp0s1  ethernet  connected      enp0s1   
   enp0s2  ethernet  disconnected    --   
   lo      loopback  unmanaged
   

   The command shows whether a device is connected or disconnected, and whether it is managed or unmanaged.

2. (Optional) Display the connection information about the network devices.

   sudo nmcli con show [--active]

   NAME     UUID                                TYPE      DEVICE
   enp0s1   nn-nn-nn-nn-nn  ethernet  enp0s1
   virbr0   nn-nn-nn-nn-nn  bridge    virbr0
   mybond   nn-nn-nn-nn-nn  bond      bond0

   The con subcommand is the short form of connection, and can be further shortened to c. Specifying the --active option would display only active devices.

   Note that in the output, NAME represents the connection ID.

3. Add a new connection.

   sudo nmcli con add {properties} [IP-info] [gateway-info

   properties

   The connection name as specified by the con-name argument, the type of connection as specified by the type argument, and the interface name as specified by the ifname argument.

   IP-info

   The IPv4 or IPv6 address as specified by either the ip4 or ip6 argument. The address must be in the format address/netmask. The IPv4 address can be in CIDR form, for example, 1.2.3.4/24.

   gateway-info

   The gateway IPv4 or IPv6 address as specified by either the gw4 or gw6 argument.

   For example, to add the connection with the information at the beginning of this procedure, you would type:

   sudo nmcli con add type ethernet ifname enp0s2 con-name "My Work Connection" ip4 192.168.5.10/24 gw4 192.168.5.2

   The output would acknowledge that the connection is successfully completed.

4. Activate the interface.

   sudo nmcli con up "My Work Connection"

5. (Optional) Display the configuration properties of the new connection.

   sudo nmcli [-o] con show "My Work Connection

   connection.id:               My Work Connection
   connection.uuid:             nn-nn-nn-nn-nn
   connection.type:             802-3-ethernet
   connection.interface-name:   enp0s2
   ...
   IP4.ADDRESS[1]:              192.168.5.10
   IP4.GATEWAY:                 192.168.5.2
   ...

   Specifying the -o option displays only properties that have configured values.

After you have created the connection, a corresponding profile is created. For more information on connection profiles, see Using NetworkManager Connection Profiles.

ls -lrt /etc/sysconfig/network-scripts/ifcfg*

...
-rw-r--r--. 1 root root 266 Aug  6 11:03 /etc/sysconfig/network-scripts/ifcfg-My_Work_Connection

To create a static route to the 192.0.2.0/24 network through the gateway 198.51.100.1, ensure first that the default gateway 198.51.100.1 is reachable on the interface. Then, complete the following steps:.

1. Start the editor.

   nm-connection-editor

2. From the list of connections, select the device under the connection name for which you want to create a static route. For example, under myconnection, you would select the device ens3.
3. Click the settings icon (gear wheel) to edit the connection settings.
4. Click the IPv4 Settings tab.
5. Click Routes.
6. Click Add.

7. Enter the network's address and netmask for which the route is created, and specify the gateway IP address through which the route is established. You can optionally enter a metric value and select the other available options on display.

   
8. Clcik OK and then save.
9. Back at the terminal window, restart the connection.

   This step causes the connection to temporarily drop.

   sudo nmcli connection up myconnection

10. Optionally, verify that the new route is active.

    ip route

    ...
    192.0.2.0/24 via 198.51.100.1 dev myconnection proto static metric 100

To configure static routes with the nmcli command, use the following syntax:

nmcli connection modify connection_name +ipv4.routes "ip[/prefix] options(s) attribute(s)"[next_hop] [metric] [attribute=value] [attribute=value] ..."

+ipv4.routes

The plus (+) sign indicates that you're creating an IPv4 route. Without the sign, the command changes an existing IPv4 setting.

connection-name

Connection name or label for which you're creating a static route.

ip[/prefix]

IP address of the static route that you're creating. The IP address can also be in CIDR notation.

options

Options include next hop addresses and optional route metrics. These options are separated by spaces. For more information, see the nm-settings-nmcli(5) manual pages.

attributes

Attributes are entered as attribute=value and are also separated by spaces. Some attributes are mtu, src, type, cwnd, and so on. For more information, see the nm-settings-nmcli(5) manual pages.

Suppose that you have the following configurations:

• Name of the connection: myconnection
• Default gateway address: 198.51.100.1
• Network to which you want to create a statci route: 192.0.2.0/24

To create the route, ensure first that the default gateway for the route is directly reachable on the interface. Then, do the following:

1. Create the static route.

   sudo nmcli connection modify myconnection +ipv4.routes "192.0.2.0/24 198.51.100.1"

   To create several static routes in a single command, separate the route gateway entries with commas, for example:

   sudo nmcli connection modify myconnection +ipv4.routes "192.0.2.0/24 198.51.100.1, 203.0.113.0/24 198.51.100.1"

2. Verify the new routing configuration.

   nmcli connection show myconnection

   –-
   ipv4.routes:   { ip = 192.0.2.0/24, nh = 198.51.100.1 }
   –-

3. Restart the network connection.

   This step causes the connection to temporarily drop.

   sudo nmcli connection up myconnection

4. Optionally, verify that the new route is active.

   ip route

   ...
   192.0.2.0/24 via 198.51.100.1 dev example proto static metric 100

You can also use the nmcli command in interactive mode to configure network settings, including configuring static routes. When in interactive mode, the nmcli> prompt appears where you can run commands to configure static routes for a specific connection profile.

The procedure in this section assumes the following network settings for creating the static route:

• Name of the connection: myconnection
• Default gateway address: 198.51.100.1
• Network to which you want to create a statci route: 192.0.2.0/24

To create the route, ensure first that the default gateway for the route is directly reachable on the interface. Then, do the following:

1. Start the command's interactive mode.

   sudo nmcli connection modify myconnection

   nmcli>

2. Create the static route.

   nmcli> set ipv4.routes 192.0.2.0/24 198.51.100.1

3. Optionally, display the new configuration.

   nmcli> print

   ...
   ipv4.routes:        { ip = 192.0.2.1/24, nh = 198.51.100.1 }
   ...

4. Save the configuration.

   nmcli> save persistent

5. Restart the network connection.

   This step causes the connection to temporarily drop.

   nmcli> activate myconnection

6. Exit the interactive mode.

   nmcli> quit

7. Optionally, verify that the new route is active.

   ip route

   ...
   192.0.2.0/24 via 198.51.100.1 dev example proto static metric 100

When creating or updating NetworkManager profile connections, we recommend using its CLI tool in offline mode (nmcli --offline). In offline mode, nmcli operates without the NetworkManager service, which offers user enhanced editing control and the ability to create various connection profiles in keyfile format. For example, you can create the following type of connection profiles in keyfile format:

• static Ethernet connection
• dynamic Ethernet connection
• network bond
• network bridge
• VLAN or any kind of enabled connections

To create a keyfile connection profile using nmcli in offline mode, follow these steps:

1. Use the required NetworkManager configuration properties to create a profile connection in offline mode.

   For example, the following syntax creates a keyfile connection profile in offline mode for an Ethernet device with a manually assigned IPv4 address and DNS address.

   nmcli --offline connection add type ethernet con-name Example-Connection ipv4.addresses ###.#.#.#/# ipv4.dns ###.#.#.### ipv4.method manual > /etc/NetworkManager/system-connections/outputmconnection

   where:

   • nmcli --offline = ncmi mode property, which instructs nmcli to operate in offline mode.
   • connection add type ethernet = add connection and type properties, which is used to create a connecton profile and specify a connection type value (in this example: Ethernet).
   • con-name = connection name property, which is saved into the id variable for the generated connection profile.
     When you manage this connection later, using nmcli, note the following id variable usages:

     • In cases where the id variable is provided, use the connection name. For example: Example-Connection.
     • In cases where the id variable is omitted, use the file name without the .nmconnection suffix, for example output.

     Note:

     For more information about connection profile properties and their settings, see the nm-settings(5) manual page.

2. Set permissions to the configuration file so that only the root user can read and update it. For example:

   chmod 600 /etc/NetworkManager/system-connections/outputmconnection
   chown root:root /etc/NetworkManager/system-connections/outputmconnection

3. Start the NetworkManager service:

   systemctl start NetworkManager.service

4. If you set the autoconnect variable in the profile to false, activate the connection:

   nmcli connection up Example-Connection

5. (Optional) To verify the profile configuration, perform these steps:

   1. Verify that the NetworkManager service is running, for example:

      systemctl status NetworkManager
      ● NetworkManager.service - Network Manager
         Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service enabled vendor preset: enabled)
         Active: active (running) because Wed -03 13:08:32 CEST   ago
      

   2. Verify that NetworkManager can read the profile from the configuration file, for example:

      nmcli -f TYPE,FILENAME,NAME connection
      TYPE      FILENAME                                                    NAME
      ethernet /etc/NetworkManager/system-connections/outputmconnection Example-Connection
      ethernet  /etc/sysconfig/network-scripts/ifcfg-enp0                 enp0
      

      If the output doesn't display the newly created connection, verify that the keyfile permissions and the syntax used are correct.

   3. To display the connection profile use the nmcli connection show command, for example:

      nmcli connection show Example-Connection
      connection.id:                          Example-Connection
      connection.uuid:                        ce8d4422-9603-4d6f-b602-4f71992c49c2
      connection.stable-id:                   --
      connection.type:                        802-3-ethernet
      connection.interface-name:              --
      connection.autoconnect:                 yes

1. If you're creating a profile for a hardware interface, such as Ethernet, display the hardware's MAC address.

   ip address show ens3

   2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast state UP group default qlen 1000
       link/ether 02:00:17:03:b9:ae brd ff:ff:ff:ff:ff:ff
       ...

2. Use any text editor to create a connection profile that contains the network settings that you want to define for the connection.

   For example, if the connection uses DHCP, the profile would contain settings similar to the following example:

   [connection]
   id=myconnection
   type=ethernet
   autoconnect=true
   
   [ipv4]
   method=auto
   
   [ipv6]
   method=auto
   
   [ethernet]
   mac-address=02:00:17:03:b9:ae

3. Save the profile to /etc/NetworkManager/system-connections/filname.nmconnection.
   In this current procedure, the profile would be /etc/NetworkManager/system-connections/myconnection.nmconnection.

   Note:

   The defined ID variable, such as myconnection, doesn't need to be identical with the profile's file name, for example myethernet.nmconnection. When you change the profile by using the nmcli command, you can identify the profile by the defined ID (myconnection) or by the file name, but excluding the file extension name (myethernet).
4. Restrict the permissions of the profile.

   sudo chown root:root /etc/NetworkManager/system-connections/myconnection.nmconnection
   sudo chown 600 /etc/NetworkManager/system-connections/myconnection.nmconnection

5. Reload the connection profiles.

   sudo nmcli connection reload

6. Verify that NetworkManager can read the profile.

   sudo nmcli -f NAME,UUID,FILENAME connection

   NAME           UUID       FILENAME
   myconnection   uuid        /etc/NetworkManager/system-connections/myconnection.nmconnection

7. If you specified false for the profile's autoconnect parameter, then activate the connection.

   sudo nmcli connection up myconnection

To convert the NetworkManager legacy ifcfg profile formats to the preferred NetworkManager keyfile format, follow these steps:

1. Ensure that the following prerequisites are met:
   • Existing connection profiles in ifcfg format that are stored in the /etc/sysconfig/network-scripts/ directory.
   • If the connection profiles contain a DEVICE variable that is set to a custom device name, such as provider or lan, you created a systemd link file or a udev rule for each of the custom device names.
2. Using the nmcli, migrate the ifcfg connection profiles to the preferred keyfile formats.

   nmcli connection migrate

3. (Optional) Verify that all the legacy ifcfg connection profiles migrated successfully:

   nmcli -f TYPE,FILENAME,NAME connection