1. The /usr/lib/udev/rules.d/60-net.rules file defines that the /lib/udev/rename_device helper utility searches for the HWADDR parameter in /etc/sysconfig/network-scripts/ifcfg-* files. If the value set in the variable matches the MAC address of an interface, the helper utility renames the interface to the name set in the DEVICE parameter of the file.
2. The /usr/lib/udev/rules.d/71-biosdevname.rules file defines that the biosdevname utility renames the interface according to its naming policy, provided that it was not renamed in the previous step.
3. The /usr/lib/udev/rules.d/75-net-description.rules file defines that udev examines the network interface device and sets the properties in udev-internal variables that will be processed in the next step. Note that some of these properties might be undefined.

4. The /usr/lib/udev/rules.d/80-net-setup-link.rules file calls the net_setup_link udev built-in which then applies the policy. The following is the default policy that is stored in the /usr/lib/systemd/network/99-default.link file:

   [Link]
   NamePolicy=kernel database onboard slot path
   MACAddressPolicy=persistent

   With this policy, if the kernel uses a persistent name, udev does not rename the interface. If the kernel does not use a persistent name, udev renames the interface to the name provided by the hardware database of udev. If this database is not available, Red Hat Enterprise Linux falls back to the mechanisms described above.

   Alternatively, set the NamePolicy parameter in this file to mac for media access control (MAC) address-based interface names.

5. The /usr/lib/udev/rules.d/80-net-setup-link.rules file defines that udev renames the interface based on the udev-internal parameters in the following order:

   1. ID_NET_NAME_ONBOARD
   2. ID_NET_NAME_SLOT
   3. ID_NET_NAME_PATH

   If one parameter is not set, udev uses the next one. If none of the parameters are set, the interface is not renamed.

Procedure

1. Boot the Red Hat Enterprise Linux installation media.

2. In the boot manager:

   1. Select the Install Red Hat Enterprise Linux <version> entry, and press Tab to edit the entry.
   2. Append net.ifnames.prefix=<prefix> to the kernel options.
   3. Press Enter to start the installer.
3. Install Red Hat Enterprise Linux.

Procedure

1. Display all network interfaces and their MAC addresses:

   # ip link list
   
   enp6s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
       link/ether b4:96:91:14:ae:58 brd ff:ff:ff:ff:ff:ff
   enp6s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
       link/ether b4:96:91:14:ae:5a brd ff:ff:ff:ff:ff:ff
   enp4s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
       link/ether 00:90:fa:6a:7d:90 brd ff:ff:ff:ff:ff:ff

2. Create the file /etc/udev/rules.d/70-custom-ifnames.rules with the following contents:

   SUBSYSTEM=="net",ACTION=="add",ATTR{address}=="b4:96:91:14:ae:58",ATTR{type}=="1",NAME="provider0"
   SUBSYSTEM=="net",ACTION=="add",ATTR{address}=="b4:96:91:14:ae:5a",ATTR{type}=="1",NAME="provider1"
   SUBSYSTEM=="net",ACTION=="add",ATTR{address}=="00:90:fa:6a:7d:90",ATTR{type}=="1",NAME="dmz"

   These rules match the MAC address of the network interfaces and rename them to the name given in the NAME property. In these examples, ATTR{type} parameter value 1 defines that the interface is of type Ethernet.

Verification

1. Reboot the system.

   # reboot

2. Verify that interface names for each MAC address match the value you set in the NAME parameter of the rule file:

   # ip link show
   
   provider0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
       link/ether b4:96:91:14:ae:58 brd ff:ff:ff:ff:ff:ff
      altname enp6s0f0
   provider1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
       link/ether b4:96:91:14:ae:5a brd ff:ff:ff:ff:ff:ff
       altname enp6s0f1
   dmz: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
       link/ether 00:90:fa:6a:7d:90 brd ff:ff:ff:ff:ff:ff
       altname enp4s0f0

Procedure

1. Display all interfaces names and their MAC addresses:

   # ip link show
   
   enp6s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
       link/ether b4:96:91:14:ae:58 brd ff:ff:ff:ff:ff:ff
   enp6s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
       link/ether b4:96:91:14:ae:5a brd ff:ff:ff:ff:ff:ff
   enp4s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
       link/ether 00:90:fa:6a:7d:90 brd ff:ff:ff:ff:ff:ff

2. For naming the interface with MAC address b4:96:91:14:ae:58 to provider0, create the /etc/systemd/network/70-custom-ifnames.link file with following contents:

   [Match]
   MACAddress=b4:96:91:14:ae:58
   
   [Link]
   Name=provider0

   This link file matches a MAC address and renames the network interface to the name set in the Name parameter.

Verification

1. Reboot the system:

   # reboot

2. Verify that the device with the MAC address you specified in the link file has been assigned to provider0:

   # ip link show
   
   provider0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
       link/ether b4:96:91:14:ae:58 brd ff:ff:ff:ff:ff:ff

Procedure

1. Create the /etc/systemd/network/10-altnames.link file with the following contents:

   [Match]
   MACAddress=52:54:00:76:e0:2a
   
   [Link]
   AlternativeName=production_alias_of_arbitrary_length
   AlternativeName=PRD

2. Reboot your system to make the changes take effect.

Procedure

1. Add a new NetworkManager connection profile for the Ethernet connection:

   # nmcli connection add con-name Example-Connection ifname enp7s0 type ethernet

   The further steps modify the Example-Connection connection profile you created.

2. Set the IPv4 address:

   # nmcli connection modify Example-Connection ipv4.addresses 192.0.2.1/24

3. Set the IPv6 address:

   # nmcli connection modify Example-Connection ipv6.addresses 2001:db8:1::1/64

4. Set the IPv4 and IPv6 connection method to manual:

   # nmcli connection modify Example-Connection ipv4.method manual
   # nmcli connection modify Example-Connection ipv6.method manual

5. Set the IPv4 and IPv6 default gateways:

   # nmcli connection modify Example-Connection ipv4.gateway 192.0.2.254
   # nmcli connection modify Example-Connection ipv6.gateway 2001:db8:1::fffe

6. Set the IPv4 and IPv6 DNS server addresses:

   # nmcli connection modify Example-Connection ipv4.dns "192.0.2.200"
   # nmcli connection modify Example-Connection ipv6.dns "2001:db8:1::ffbb"

   To set multiple DNS servers, specify them space-separated and enclosed in quotes.

7. Set the DNS search domain for the IPv4 and IPv6 connection:

   # nmcli connection modify Example-Connection ipv4.dns-search example.com
   # nmcli connection modify Example-Connection ipv6.dns-search example.com

8. Activate the connection profile:

   # nmcli connection up Example-Connection
   Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/13)

Verification

1. Display the status of the devices and connections:

   # nmcli device status
   DEVICE      TYPE      STATE      CONNECTION
   enp7s0      ethernet  connected  Example-Connection

2. Use the ping utility to verify that this host can send packets to other hosts:

   # ping host_name_or_IP_address

Procedure

1. To add a new NetworkManager connection profile for the Ethernet connection, and starting the interactive mode, enter:

   # nmcli connection edit type ethernet con-name Example-Connection

2. Set the network interface:

   nmcli> set connection.interface-name enp7s0

3. Set the IPv4 address:

   nmcli> set ipv4.addresses 192.0.2.1/24

4. Set the IPv6 address:

   nmcli> set ipv6.addresses 2001:db8:1::1/64

5. Set the IPv4 and IPv6 connection method to manual:

   nmcli> set ipv4.method manual
   nmcli> set ipv6.method manual

6. Set the IPv4 and IPv6 default gateways:

   nmcli> set ipv4.gateway 192.0.2.254
   nmcli> set ipv6.gateway 2001:db8:1::fffe

7. Set the IPv4 and IPv6 DNS server addresses:

   nmcli> set ipv4.dns 192.0.2.200
   nmcli> set ipv6.dns 2001:db8:1::ffbb

   To set multiple DNS servers, specify them space-separated and enclosed in quotation marks.

8. Set the DNS search domain for the IPv4 and IPv6 connection:

   nmcli> set ipv4.dns-search example.com
   nmcli> set ipv6.dns-search example.com

9. Save and activate the connection:

   nmcli> save persistent
   Saving the connection with 'autoconnect=yes'. That might result in an immediate activation of the connection.
   Do you still want to save? (yes/no) [yes] yes

10. Leave the interactive mode:

    nmcli> quit

Verification

1. Display the status of the devices and connections:

   # nmcli device status
   DEVICE      TYPE      STATE      CONNECTION
   enp7s0      ethernet  connected  Example-Connection

2. Use the ping utility to verify that this host can send packets to other hosts:

   # ping host_name_or_IP_address

Procedure

1. If you do not know the network device name you want to use in the connection, display the available devices:

   # nmcli device status
   DEVICE     TYPE      STATE                   CONNECTION
   enp7s0     ethernet  unavailable             --
   ...

2. Start nmtui:

   # nmtui

3. Select Edit a connection, and press Enter.
4. Press the Add button.
5. Select Ethernet from the list of network types, and press Enter.
6. Optional: Enter a name for the NetworkManager profile to be created.
7. Enter the network device name into the Device field.

8. Configure the IPv4 and IPv6 address settings in the IPv4 configuration and IPv6 configuration areas:

   1. Press the Automatic button, and select Manual from the displayed list.
   2. Press the Show button next to the protocol you want to configure to display additional fields.

   3. Press the Add button next to Addresses, and enter the IP address and the subnet mask in Classless Inter-Domain Routing (CIDR) format.

      If you do not specify a subnet mask, NetworkManager sets a /32 subnet mask for IPv4 addresses and /64 for IPv6 addresses.

   4. Enter the address of the default gateway.
   5. Press the Add button next to DNS servers, and enter the DNS server address.
   6. Press the Add button next to Search domains, and enter the DNS search domain.

   Figure 2.1. Example of an Ethernet connection with static IP address settings

   
9. Press the OK button to create and automatically activate the new connection.
10. Press the Back button to return to the main menu.
11. Select Quit, and press Enter to close the nmtui application.

Verification

1. Display the status of the devices and connections:

   # nmcli device status
   DEVICE      TYPE      STATE      CONNECTION
   enp7s0      ethernet  connected  Example-Connection

2. Use the ping utility to verify that this host can send packets to other hosts:

   # ping host_name_or_IP_address

Procedure

1. Create a YAML file, for example ~/create-ethernet-profile.yml, with the following contents:

   ---
   interfaces:
   - name: enp7s0
     type: ethernet
     state: up
     ipv4:
       enabled: true
       address:
       - ip: 192.0.2.1
         prefix-length: 24
       dhcp: false
     ipv6:
       enabled: true
       address:
       - ip: 2001:db8:1::1
         prefix-length: 64
       autoconf: false
       dhcp: false
   routes:
     config:
     - destination: 0.0.0.0/0
       next-hop-address: 192.0.2.254
       next-hop-interface: enp7s0
     - destination: ::/0
       next-hop-address: 2001:db8:1::fffe
       next-hop-interface: enp7s0
   dns-resolver:
     config:
       search:
       - example.com
       server:
       - 192.0.2.200
       - 2001:db8:1::ffbb

2. Apply the settings to the system:

   # nmstatectl apply ~/create-ethernet-profile.yml

Verification

1. Display the status of the devices and connections:

   # nmcli device status
   DEVICE      TYPE      STATE      CONNECTION
   enp7s0      ethernet  connected  enp7s0

2. Display all settings of the connection profile:

   # nmcli connection show enp7s0
   connection.id:              enp7s0
   connection.uuid:            b6cdfa1c-e4ad-46e5-af8b-a75f06b79f76
   connection.stable-id:       --
   connection.type:            802-3-ethernet
   connection.interface-name:  enp7s0
   ...

3. Display the connection settings in YAML format:

   # nmstatectl show enp7s0

Procedure

1. Create a playbook file, for example ~/ethernet-static-IP.yml, with the following content:

   ---
   - name: Configure the network
     hosts: managed-node-01.example.com
     tasks:
     - name: Configure an Ethernet connection with static IP
       include_role:
         name: rhel-system-roles.network
   
       vars:
         network_connections:
           - name: enp7s0
             interface_name: enp7s0
             type: ethernet
             autoconnect: yes
             ip:
               address:
                 - 192.0.2.1/24
                 - 2001:db8:1::1/64
               gateway4: 192.0.2.254
               gateway6: 2001:db8:1::fffe
               dns:
                 - 192.0.2.200
                 - 2001:db8:1::ffbb
               dns_search:
                 - example.com
             state: up

2. Run the playbook:

   # ansible-playbook ~/ethernet-static-IP.yml

Procedure

1. Create a playbook file, for example ~/ethernet-static-IP.yml, with the following content:

   ---
   - name: Configure the network
     hosts: managed-node-01.example.com
     tasks:
     - name: Configure an Ethernet connection with static IP
       include_role:
         name: rhel-system-roles.network
   
       vars:
         network_connections:
           - name: example
             match:
               path:
                 - pci-0000:00:0[1-3].0
                 - &!pci-0000:00:02.0
             type: ethernet
             autoconnect: yes
             ip:
               address:
                 - 192.0.2.1/24
                 - 2001:db8:1::1/64
               gateway4: 192.0.2.254
               gateway6: 2001:db8:1::fffe
               dns:
                 - 192.0.2.200
                 - 2001:db8:1::ffbb
               dns_search:
                 - example.com
             state: up

   The match parameter in this example defines that Ansible applies the play to devices that match PCI ID 0000:00:0[1-3].0, but not 0000:00:02.0. For further details about special modifiers and wild cards you can use, see the match parameter description in the /usr/share/ansible/roles/rhel-system-roles.network/README.md file.

2. Run the playbook:

   # ansible-playbook ~/ethernet-static-IP.yml

Procedure

1. Add a new NetworkManager connection profile for the Ethernet connection:

   # nmcli connection add con-name Example-Connection ifname enp7s0 type ethernet

2. Optionally, change the host name NetworkManager sends to the DHCP server when using the Example-Connection profile:

   # nmcli connection modify Example-Connection ipv4.dhcp-hostname Example ipv6.dhcp-hostname Example

3. Optionally, change the client ID NetworkManager sends to an IPv4 DHCP server when using the Example-Connection profile:

   # nmcli connection modify Example-Connection ipv4.dhcp-client-id client-ID

   Note that there is no dhcp-client-id parameter for IPv6. To create an identifier for IPv6, configure the dhclient service.

Verification

1. Display the status of the devices and connections:

   # nmcli device status
   DEVICE      TYPE      STATE      CONNECTION
   enp7s0      ethernet  connected  Example-Connection

2. Use the ping utility to verify that this host can send packets to other hosts:

   # ping host_name_or_IP_address

Procedure

1. To add a new NetworkManager connection profile for the Ethernet connection, and starting the interactive mode, enter:

   # nmcli connection edit type ethernet con-name Example-Connection

2. Set the network interface:

   nmcli> set connection.interface-name enp7s0

3. Optionally, change the host name NetworkManager sends to the DHCP server when using the Example-Connection profile:

   nmcli> set ipv4.dhcp-hostname Example
   nmcli> set ipv6.dhcp-hostname Example

4. Optionally, change the client ID NetworkManager sends to an IPv4 DHCP server when using the Example-Connection profile:

   nmcli> set ipv4.dhcp-client-id client-ID

   Note that there is no dhcp-client-id parameter for IPv6. To create an identifier for IPv6, configure the dhclient service.

5. Save and activate the connection:

   nmcli> save persistent
   Saving the connection with 'autoconnect=yes'. That might result in an immediate activation of the connection.
   Do you still want to save? (yes/no) [yes] yes

6. Leave the interactive mode:

   nmcli> quit

Verification

1. Display the status of the devices and connections:

   # nmcli device status
   DEVICE      TYPE      STATE      CONNECTION
   enp7s0      ethernet  connected  Example-Connection

2. Use the ping utility to verify that this host can send packets to other hosts:

   # ping host_name_or_IP_address

Procedure

1. If you do not know the network device name you want to use in the connection, display the available devices:

   # nmcli device status
   DEVICE     TYPE      STATE                   CONNECTION
   enp7s0     ethernet  unavailable             --
   ...

2. Start nmtui:

   # nmtui

3. Select Edit a connection, and press Enter.
4. Press the Add button.
5. Select Ethernet from the list of network types, and press Enter.
6. Optional: Enter a name for the NetworkManager profile to be created.
7. Enter the network device name into the Device field.

8. Press the OK button to create and automatically activate the new connection.

   
9. Press the Back button to return to the main menu.
10. Select Quit, and press Enter to close the nmtui application.

Verification

1. Display the status of the devices and connections:

   # nmcli device status
   DEVICE      TYPE      STATE      CONNECTION
   enp7s0      ethernet  connected  Example-Connection

2. Use the ping utility to verify that this host can send packets to other hosts:

   # ping host_name_or_IP_address

Procedure

1. Create a YAML file, for example ~/create-ethernet-profile.yml, with the following contents:

   ---
   interfaces:
   - name: enp7s0
     type: ethernet
     state: up
     ipv4:
       enabled: true
       auto-dns: true
       auto-gateway: true
       auto-routes: true
       dhcp: true
     ipv6:
       enabled: true
       auto-dns: true
       auto-gateway: true
       auto-routes: true
       autoconf: true
       dhcp: true

2. Apply the settings to the system:

   # nmstatectl apply ~/create-ethernet-profile.yml

Verification

1. Display the status of the devices and connections:

   # nmcli device status
   DEVICE      TYPE      STATE      CONNECTION
   enp7s0      ethernet  connected  enp7s0

2. Display all settings of the connection profile:

   # nmcli connection show enp7s0
   connection.id:              enp7s0
   connection.uuid:            b6cdfa1c-e4ad-46e5-af8b-a75f06b79f76
   connection.stable-id:       --
   connection.type:            802-3-ethernet
   connection.interface-name:  enp7s0
   ...

3. Display the connection settings in YAML format:

   # nmstatectl show enp7s0

Procedure

1. Create a playbook file, for example ~/ethernet-dynamic-IP.yml, with the following content:

   ---
   - name: Configure the network
     hosts: managed-node-01.example.com
     tasks:
     - name: Configure an Ethernet connection with dynamic IP
       include_role:
         name: rhel-system-roles.network
   
       vars:
         network_connections:
           - name: enp7s0
             interface_name: enp7s0
             type: ethernet
             autoconnect: yes
             ip:
               dhcp4: yes
               auto6: yes
             state: up

2. Run the playbook:

   # ansible-playbook ~/ethernet-dynamic-IP.yml

Procedure

1. Create a playbook file, for example ~/ethernet-dynamic-IP.yml, with the following content:

   ---
   - name: Configure the network
     hosts: managed-node-01.example.com
     tasks:
     - name: Configure an Ethernet connection with dynamic IP
       include_role:
         name: rhel-system-roles.network
   
       vars:
         network_connections:
           - name: example
             match:
               path:
                 - pci-0000:00:0[1-3].0
                 - &!pci-0000:00:02.0
             type: ethernet
             autoconnect: yes
             ip:
               dhcp4: yes
               auto6: yes
             state: up

   The match parameter in this example defines that Ansible applies the play to devices that match PCI ID 0000:00:0[1-3].0, but not 0000:00:02.0. For further details about special modifiers and wild cards you can use, see the match parameter description in the /usr/share/ansible/roles/rhel-system-roles.network/README.md file.

2. Run the playbook:

   # ansible-playbook ~/ethernet-dynamic-IP.yml

Procedure

1. Press the Super key, enter Settings, and press Enter.
2. Select Network in the navigation on the left.
3. Click the + button next to the Wired entry to create a new profile.
4. Optional: Set a name for the connection on the Identity tab.

5. On the IPv4 tab, configure the IPv4 settings. For example, select method Manual, set a static IPv4 address, network mask, default gateway, and DNS server:

   

6. On the IPv6 tab, configure the IPv6 settings. For example, select method Manual, set a static IPv6 address, network mask, default gateway, and DNS server:

   
7. Click the Add button to save the connection. The GNOME control-center automatically activates the connection.

Verification

1. Display the status of the devices and connections:

   # nmcli device status
   DEVICE      TYPE      STATE      CONNECTION
   enp7s0      ethernet  connected  Example-Connection

2. Use the ping utility to verify that this host can send packets to other hosts:

   # ping host_name_or_IP_address

Procedure

1. Open a terminal, and enter:

   $ nm-connection-editor

2. Click the + button to add a new connection.
3. Select the Ethernet connection type, and click Create.

4. On the General tab:

   1. To automatically enable this connection when the system boots or when you restart the NetworkManager service:

      1. Select Connect automatically with priority.

      2. Optional: Change the priority value next to Connect automatically with priority.

         If multiple connection profiles exist for the same device, NetworkManager enables only one profile. By default, NetworkManager activates the last-used profile that has auto-connect enabled. However, if you set priority values in the profiles, NetworkManager activates the profile with the highest priority.

   2. Clear the All users may connect to this network check box if the profile should be available only to the user that created the connection profile.

   

5. On the Ethernet tab, select a device and, optionally, further Ethernet-related settings.

   

6. On the IPv4 Settings tab, configure the IPv4 settings. For example, set a static IPv4 address, network mask, default gateway, and DNS server:

   

7. On the IPv6 Settings tab, configure the IPv6 settings. For example, set a static IPv6 address, network mask, default gateway, and DNS server:

   

8. Save the connection.
9. Close nm-connection-editor.

Verification

1. Display the status of the devices and connections:

   # nmcli device status
   DEVICE      TYPE      STATE      CONNECTION
   enp7s0      ethernet  connected  Example-Connection

2. Use the ping utility to verify that this host can send packets to other hosts:

   # ping host_name_or_IP_address

Procedure

1. Create the /etc/NetworkManager/conf.d/dhcp-client.conf file with the following content:

   [main]
   dhcp=dhclient

   You can set the dhcp parameter to internal (default) or dhclient.

2. If you set the dhcp parameter to dhclient, install the dhcp-client package:

   # yum install dhcp-client

3. Restart NetworkManager:

   # systemctl restart NetworkManager

   Note that the restart temporarily interrupts all network connections.

Procedure

1. Set the ipv4.dhcp-timeout and ipv6.dhcp-timeout properties. For example, to set both options to 30 seconds, enter:

   # nmcli connection modify connection_name ipv4.dhcp-timeout 30 ipv6.dhcp-timeout 30

   Alternatively, set the parameters to infinity to configure that NetworkManager does not stop trying to request and renew an IP address until it is successful.

2. Optional: Configure the behavior if NetworkManager does not receive an IPv4 address before the timeout:

   # nmcli connection modify connection_name ipv4.may-fail value

   If you set the ipv4.may-fail option to:

   • yes, the status of the connection depends on the IPv6 configuration:

     • If the IPv6 configuration is enabled and successful, NetworkManager activates the IPv6 connection and no longer tries to activate the IPv4 connection.
     • If the IPv6 configuration is disabled or not configured, the connection fails.

   • no, the connection is deactivated. In this case:

     • If the autoconnect property of the connection is enabled, NetworkManager retries to activate the connection as many times as set in the autoconnect-retries property. The default is 4.
     • If the connection still cannot acquire a DHCP address, auto-activation fails. Note that after 5 minutes, the auto-connection process starts again to acquire an IP address from the DHCP server.

3. Optional: Configure the behavior if NetworkManager does not receive an IPv6 address before the timeout:

   # nmcli connection modify connection_name ipv6.may-fail value

Procedure

1. Add a connection profile that applies to all interface names starting with enp:

   # nmcli connection add con-name Example connection.multi-connect multiple match.interface-name enp* type ethernet

Verification

1. Display all settings of the single connection profile:

   # nmcli connection show Example
   connection.id:                      Example
   ...
   connection.multi-connect:           3 (multiple)
   match.interface-name:               enp*
   ...

   3 indicates the number of interfaces active on the connection profile at the same time, and not the number of network interfaces in the connection profile. The connection profile uses all devices that match the pattern in the match.interface-name parameter and, therefore, the connection profiles have the same Universally Unique Identifier (UUID).

2. Display the status of the connections:

   # nmcli connection show
   NAME                    UUID                    TYPE     DEVICE
   ...
   Example  6f22402e-c0cc-49cf-b702-eaf0cd5ea7d1  ethernet  enp7s0
   Example  6f22402e-c0cc-49cf-b702-eaf0cd5ea7d1  ethernet  enp8s0
   Example  6f22402e-c0cc-49cf-b702-eaf0cd5ea7d1  ethernet  enp9s0

Procedure

1. Identify the device path. For example, to display the device paths of all interfaces starting with enp, enter :

   # udevadm info /sys/class/net/enp* | grep ID_PATH=
   ...
   E: ID_PATH=pci-0000:07:00.0
   E: ID_PATH=pci-0000:08:00.0

2. Add a connection profile that applies to all PCI IDs matching the 0000:00:0[7-8].0 expression:

   # nmcli connection add type ethernet connection.multi-connect multiple match.path "pci-0000:07:00.0 pci-0000:08:00.0" con-name Example

Verification

1. Display the status of the connection:

   # nmcli connection show
   NAME   UUID     TYPE        DEVICE
   Example      9cee0958-512f-4203-9d3d-b57af1d88466  ethernet  enp7s0
   Example      9cee0958-512f-4203-9d3d-b57af1d88466  ethernet  enp8s0
   ...

2. To display all settings of the connection profile:

   # nmcli connection show Example
   connection.id:               Example
   ...
   connection.multi-connect:    3 (multiple)
   match.path:                  pci-0000:07:00.0,pci-0000:08:00.0
   ...

   This connection profile uses all devices with a PCI ID which match the pattern in the match.path parameter and, therefore, the connection profiles have the same Universally Unique Identifier (UUID).

Procedure

1. Create a bond interface:

   # nmcli connection add type bond con-name bond0 ifname bond0 bond.options "mode=active-backup"

   This command creates a bond named bond0 that uses the active-backup mode.

   To additionally set a Media Independent Interface (MII) monitoring interval, add the miimon=interval option to the bond.options property, for example:

   # nmcli connection add type bond con-name bond0 ifname bond0 bond.options "mode=active-backup,miimon=1000"

2. Display the network interfaces, and note names of interfaces you plan to add to the bond:

   # nmcli device status
   DEVICE   TYPE      STATE         CONNECTION
   enp7s0   ethernet  disconnected  --
   enp8s0   ethernet  disconnected  --
   bridge0  bridge    connected     bridge0
   bridge1  bridge    connected     bridge1
   ...

   In this example:

   • enp7s0 and enp8s0 are not configured. To use these devices as ports, add connection profiles in the next step.
   • bridge0 and bridge1 have existing connection profiles. To use these devices as ports, modify their profiles in the next step.

3. Assign interfaces to the bond:

   1. If the interfaces you want to assign to the bond are not configured, create new connection profiles for them:

      # nmcli connection add type ethernet slave-type bond con-name bond0-port1 ifname enp7s0 master bond0
      # nmcli connection add type ethernet slave-type bond con-name bond0-port2 ifname enp8s0 master bond0

      These commands create profiles for enp7s0 and enp8s0, and add them to the bond0 connection.

   2. To assign an existing connection profile to the bond:

      1. Set the master parameter of these connections to bond0:

         # nmcli connection modify bridge0 master bond0
         # nmcli connection modify bridge1 master bond0

         These commands assign the existing connection profiles named bridge0 and bridge1 to the bond0 connection.

      2. Reactivate the connections:

         # nmcli connection up bridge0
         # nmcli connection up bridge1

4. Configure the IPv4 settings:

   • To use this bond device as a port of other devices, enter:

     # nmcli connection modify bond0 ipv4.method disabled

   • To use DHCP, no action is required.

   • To set a static IPv4 address, network mask, default gateway, and DNS server to the bond0 connection, enter:

     # nmcli connection modify bond0 ipv4.addresses '192.0.2.1/24' ipv4.gateway '192.0.2.254' ipv4.dns '192.0.2.253' ipv4.dns-search 'example.com' ipv4.method manual

5. Configure the IPv6 settings:

   • To use this bond device as a port of other devices, enter:

     # nmcli connection modify bond0 ipv6.method disabled

   • To use DHCP, no action is required.

   • To set a static IPv6 address, network mask, default gateway, and DNS server to the bond0 connection, enter:

     # nmcli connection modify bond0 ipv6.addresses '2001:db8:1::1/64' ipv6.gateway '2001:db8:1::fffe' ipv6.dns '2001:db8:1::fffd' ipv6.dns-search 'example.com' ipv6.method manual

6. Optional: If you want to set any parameters on the bond ports, use the following command:

   # nmcli connection modify bond0-port1 bond-port.<parameter> <value>

7. Activate the connection:

   # nmcli connection up bond0

8. Verify that the ports are connected, and the CONNECTION column displays the port’s connection name:

   # nmcli device
   DEVICE   TYPE      STATE      CONNECTION
   ...
   enp7s0   ethernet  connected  bond0-port1
   enp8s0   ethernet  connected  bond0-port2

   When you activate any port of the connection, NetworkManager also activates the bond, but not the other ports of it. You can configure that Red Hat Enterprise Linux enables all ports automatically when the bond is enabled:

   1. Enable the connection.autoconnect-slaves parameter of the bond’s connection:

      # nmcli connection modify bond0 connection.autoconnect-slaves 1

   2. Reactivate the bridge:

      # nmcli connection up bond0

Verification

1. Temporarily remove the network cable from the host.

   Note that there is no method to properly test link failure events using software utilities. Tools that deactivate connections, such as nmcli, show only the bonding driver’s ability to handle port configuration changes and not actual link failure events.

2. Display the status of the bond:

   # cat /proc/net/bonding/bond0

Procedure

1. Select the Networking tab in the navigation on the left side of the screen.
2. Click Add bond in the Interfaces section.
3. Enter the name of the bond device you want to create.
4. Select the interfaces that should be members of the bond.

5. Select the mode of the bond.

   If you select Active backup, the web console shows the additional field Primary in which you can select the preferred active device.

6. Set the link monitoring mode. For example, when you use the Adaptive load balancing mode, set it to ARP.

7. Optional: Adjust the monitoring interval, link up delay, and link down delay settings. Typically, you only change the defaults for troubleshooting purposes.

   
8. Click Apply.

9. By default, the bond uses a dynamic IP address. If you want to set a static IP address:

   1. Click the name of the bond in the Interfaces section.
   2. Click Edit next to the protocol you want to configure.
   3. Select Manual next to Addresses, and enter the IP address, prefix, and default gateway.
   4. In the DNS section, click the + button, and enter the IP address of the DNS server. Repeat this step to set multiple DNS servers.
   5. In the DNS search domains section, click the + button, and enter the search domain.

   6. If the interface requires static routes, configure them in the Routes section.

      
   7. Click Apply

Verification

1. Select the Networking tab in the navigation on the left side of the screen, and check if there is incoming and outgoing traffic on the interface:

   

2. Temporarily remove the network cable from the host.

   Note that there is no method to properly test link failure events using software utilities. Tools that deactivate connections, such as the web console, show only the bonding driver’s ability to handle member configuration changes and not actual link failure events.

3. Display the status of the bond:

   # cat /proc/net/bonding/bond0

Procedure

1. If you do not know the network device names on which you want configure a network bond, display the available devices:

   # nmcli device status
   DEVICE     TYPE      STATE                   CONNECTION
   enp7s0     ethernet  unavailable             --
   enp8s0     ethernet  unavailable             --
   ...

2. Start nmtui:

   # nmtui

3. Select Edit a connection, and press Enter.
4. Press the Add button.
5. Select Bond from the list of network types, and press Enter.
6. Optional: Enter a name for the NetworkManager profile to be created.
7. Enter the bond device name to be created into the Device field.

8. Add ports to the bond to be created:

   1. Press the Add button next to the Slaves list.
   2. Select the type of the interface you want to add as port to the bond, for example, Ethernet.
   3. Optional: Enter a name for the NetworkManager profile to be created for this bond port.
   4. Enter the port’s device name into the Device field.

   5. Press the OK button to return to the window with the bond settings.

      Figure 3.1. Adding an Ethernet device as port to a bond

      
   6. Repeat these steps to add more ports to the bond.
9. Set the bond mode. Depending on the value you set, nmtui displays additional fields for settings that are related to the selected mode.

10. Depending on your environment, configure the IP address settings in the IPv4 configuration and IPv6 configuration areas accordingly. For this, press the Automatic button, and select:

    • Disabled, if the bond does not require an IP address.
    • Automatic, if a DHCP server dynamically assigns an IP address to the bond.

    • Manual, if the network requires static IP address settings. In this case, you must fill further fields:

      1. Press the Show button next to the protocol you want to configure to display additional fields.

      2. Press the Add button next to Addresses, and enter the IP address and the subnet mask in Classless Inter-Domain Routing (CIDR) format.

         If you do not specify a subnet mask, NetworkManager sets a /32 subnet mask for IPv4 addresses and /64 for IPv6 addresses.

      3. Enter the address of the default gateway.
      4. Press the Add button next to DNS servers, and enter the DNS server address.
      5. Press the Add button next to Search domains, and enter the DNS search domain.

    Figure 3.2. Example of a bond connection with static IP address settings

    
11. Press the OK button to create and automatically activate the new connection.
12. Press the Back button to return to the main menu.
13. Select Quit, and press Enter to close the nmtui application.

Verification

1. Temporarily remove the network cable from the host.

   Note that there is no method to properly test link failure events using software utilities. Tools that deactivate connections, such as nmcli, show only the bonding driver’s ability to handle port configuration changes and not actual link failure events.

2. Display the status of the bond:

   # cat /proc/net/bonding/bond0

Procedure

1. Open a terminal, and enter nm-connection-editor:

   $ nm-connection-editor

2. Click the + button to add a new connection.
3. Select the Bond connection type, and click Create.

4. On the Bond tab:

   1. Optional: Set the name of the bond interface in the Interface name field.

   2. Click the Add button to add a network interface as a port to the bond.

      1. Select the connection type of the interface. For example, select Ethernet for a wired connection.
      2. Optional: Set a connection name for the port.
      3. If you create a connection profile for an Ethernet device, open the Ethernet tab, and select in the Device field the network interface you want to add as a port to the bond. If you selected a different device type, configure it accordingly. Note that you can only use Ethernet interfaces in a bond that are not configured.
      4. Click Save.

   3. Repeat the previous step for each interface you want to add to the bond:

      

   4. Optional: Set other options, such as the Media Independent Interface (MII) monitoring interval.

5. Configure the IP address settings on both the IPv4 Settings and IPv6 Settings tabs:

   • To use this bridge device as a port of other devices, set the Method field to Disabled.
   • To use DHCP, leave the Method field at its default, Automatic (DHCP).

   • To use static IP settings, set the Method field to Manual and fill the fields accordingly:

     

6. Click Save.
7. Close nm-connection-editor.

Verification

1. Temporarily remove the network cable from the host.

   Note that there is no method to properly test link failure events using software utilities. Tools that deactivate connections, such as nmcli, show only the bonding driver’s ability to handle port configuration changes and not actual link failure events.

2. Display the status of the bond:

   # cat /proc/net/bonding/bond0

Procedure

1. Create a YAML file, for example ~/create-bond.yml, with the following contents:

   ---
   interfaces:
   - name: bond0
     type: bond
     state: up
     ipv4:
       enabled: true
       address:
       - ip: 192.0.2.1
         prefix-length: 24
       dhcp: false
     ipv6:
       enabled: true
       address:
       - ip: 2001:db8:1::1
         prefix-length: 64
       autoconf: false
       dhcp: false
     link-aggregation:
       mode: active-backup
       port:
       - enp1s0
       - enp7s0
   - name: enp1s0
     type: ethernet
     state: up
   - name: enp7s0
     type: ethernet
     state: up
   
   routes:
     config:
     - destination: 0.0.0.0/0
       next-hop-address: 192.0.2.254
       next-hop-interface: bond0
     - destination: ::/0
       next-hop-address: 2001:db8:1::fffe
       next-hop-interface: bond0
   
   dns-resolver:
     config:
       search:
       - example.com
       server:
       - 192.0.2.200
       - 2001:db8:1::ffbb

2. Apply the settings to the system:

   # nmstatectl apply ~/create-bond.yml

Verification

1. Display the status of the devices and connections:

   # nmcli device status
   DEVICE      TYPE      STATE      CONNECTION
   bond0       bond      connected  bond0

2. Display all settings of the connection profile:

   # nmcli connection show bond0
   connection.id:              bond0
   connection.uuid:            79cbc3bd-302e-4b1f-ad89-f12533b818ee
   connection.stable-id:       --
   connection.type:            bond
   connection.interface-name:  bond0
   ...

3. Display the connection settings in YAML format:

   # nmstatectl show bond0

Procedure

1. Create a playbook file, for example ~/bond-ethernet.yml, with the following content:

   ---
   - name: Configure the network
     hosts: managed-node-01.example.com
     tasks:
     - name: Configure a network bond that uses two Ethernet ports
       include_role:
         name: rhel-system-roles.network
   
       vars:
         network_connections:
           # Define the bond profile
           - name: bond0
             type: bond
             interface_name: bond0
             ip:
               address:
                 - "192.0.2.1/24"
                 - "2001:db8:1::1/64"
               gateway4: 192.0.2.254
               gateway6: 2001:db8:1::fffe
               dns:
                 - 192.0.2.200
                 - 2001:db8:1::ffbb
               dns_search:
                 - example.com
             bond:
               mode: active-backup
             state: up
   
           # Add an Ethernet profile to the bond
           - name: bond0-port1
             interface_name: enp7s0
             type: ethernet
             controller: bond0
             state: up
   
           # Add a second Ethernet profile to the bond
           - name: bond0-port2
             interface_name: enp8s0
             type: ethernet
             controller: bond0
             state: up

2. Run the playbook:

   # ansible-playbook ~/bond-ethernet.yml

Procedure

1. Create a bond interface in active-backup mode:

   # nmcli connection add type bond con-name bond0 ifname bond0 bond.options "mode=active-backup"

   This command names both the interface and connection profile bond0.

2. Configure the IPv4 settings of the bond:

   • If a DHCP server in your network assigns IPv4 addresses to hosts, no action is required.

   • If your local network requires static IPv4 addresses, set the address, network mask, default gateway, DNS server, and DNS search domain to the bond0 connection:

     # nmcli connection modify bond0 ipv4.addresses '192.0.2.1/24'
     # nmcli connection modify bond0 ipv4.gateway '192.0.2.254'
     # nmcli connection modify bond0 ipv4.dns '192.0.2.253'
     # nmcli connection modify bond0 ipv4.dns-search 'example.com'
     # nmcli connection modify bond0 ipv4.method manual

3. Configure the IPv6 settings of the bond:

   • If your router or a DHCP server in your network assigns IPv6 addresses to hosts, no action is required.

   • If your local network requires static IPv6 addresses, set the address, network mask, default gateway, DNS server, and DNS search domain to the bond0 connection:

     # nmcli connection modify bond0 ipv6.addresses '2001:db8:1::1/64'
     # nmcli connection modify bond0 ipv6.gateway '2001:db8:1::fffe'
     # nmcli connection modify bond0 ipv6.dns '2001:db8:1::fffd'
     # nmcli connection modify bond0 ipv6.dns-search 'example.com'
     # nmcli connection modify bond0 ipv6.method manual

4. Display the connection profiles:

   # nmcli connection show
   NAME             UUID                                  TYPE      DEVICE
   Docking_station  256dd073-fecc-339d-91ae-9834a00407f9  ethernet  enp11s0u1
   Wi-Fi            1f1531c7-8737-4c60-91af-2d21164417e8  wifi      wlp1s0
   ...

   You require the names of the connection profiles and the Ethernet device name in the next steps.

5. Assign the connection profile of the Ethernet connection to the bond:

   # nmcli connection modify Docking_station master bond0

6. Assign the connection profile of the Wi-Fi connection to the bond:

   # nmcli connection modify Wi-Fi master bond0

7. If your Wi-Fi network uses MAC filtering to allow only MAC addresses on a allow list to access the network, configure that NetworkManager dynamically assigns the MAC address of the active port to the bond:

   # nmcli connection modify bond0 +bond.options fail_over_mac=1

   With this setting, you must set only the MAC address of the Wi-Fi device to the allow list instead of the MAC address of both the Ethernet and Wi-Fi device.

8. Set the device associated with the Ethernet connection as primary device of the bond:

   # nmcli con modify bond0 +bond.options "primary=enp11s0u1"

   With this setting, the bond always uses the Ethernet connection if it is available.

9. Configure that NetworkManager automatically activates ports when the bond0 device is activated:

   # nmcli connection modify bond0 connection.autoconnect-slaves 1

10. Activate the bond0 connection:

    # nmcli connection up bond0

Procedure

1. Create a team interface:

   # nmcli connection add type team con-name team0 ifname team0 team.runner activebackup

   This command creates a network team named team0 that uses the activebackup runner.

2. Optionally, set a link watcher. For example, to set the ethtool link watcher in the team0 connection profile:

   # nmcli connection modify team0 team.link-watchers "name=ethtool"

   Link watchers support different parameters. To set parameters for a link watcher, specify them space-separated in the name property. Note that the name property must be surrounded by quotation marks. For example, to use the ethtool link watcher and set its delay-up parameter to 2500 milliseconds (2.5 seconds):

   # nmcli connection modify team0 team.link-watchers "name=ethtool delay-up=2500"

   To set multiple link watchers and each of them with specific parameters, the link watchers must be separated by a comma. The following example sets the ethtool link watcher with the delay-up parameter and the arp_ping link watcher with the source-host and target-host parameter:

   # nmcli connection modify team0 team.link-watchers "name=ethtool delay-up=2, name=arp_ping source-host=192.0.2.1 target-host=192.0.2.2"

3. Display the network interfaces, and note the names of the interfaces you want to add to the team:

   # nmcli device status
   DEVICE  TYPE      STATE         CONNECTION
   enp7s0  ethernet  disconnected  --
   enp8s0  ethernet  disconnected  --
   bond0   bond      connected  bond0
   bond1   bond      connected  bond1
   ...

   In this example:

   • enp7s0 and enp8s0 are not configured. To use these devices as ports, add connection profiles in the next step. Note that you can only use Ethernet interfaces in a team that are not assigned to any connection.
   • bond0 and bond1 have existing connection profiles. To use these devices as ports, modify their profiles in the next step.

4. Assign the port interfaces to the team:

   1. If the interfaces you want to assign to the team are not configured, create new connection profiles for them:

      # nmcli connection add type ethernet slave-type team con-name team0-port1 ifname enp7s0 master team0
      # nmcli connection add type ethernet slave-type team con-name team0-port2 ifname enp8s0 master team0

      . These commands create profiles for enp7s0 and enp8s0, and add them to the team0 connection.

   2. To assign an existing connection profile to the team:

      1. Set the master parameter of these connections to team0:

         # nmcli connection modify bond0 master team0
         # nmcli connection modify bond1 master team0

         These commands assign the existing connection profiles named bond0 and bond1 to the team0 connection.

      2. Reactivate the connections:

         # nmcli connection up bond0
         # nmcli connection up bond1

5. Configure the IPv4 settings:

   • To use this team device as a port of other devices, enter:

     # nmcli connection modify team0 ipv4.method disabled

   • To use DHCP, no action is required.

   • To set a static IPv4 address, network mask, default gateway, and DNS server to the team0 connection, enter:

     # nmcli connection modify team0 ipv4.addresses '192.0.2.1/24' ipv4.gateway '192.0.2.254' ipv4.dns '192.0.2.253' ipv4.dns-search 'example.com' ipv4.method manual

6. Configure the IPv6 settings:

   • To use this team device as a port of other devices, enter:

     # nmcli connection modify team0 ipv6.method disabled

   • To use DHCP, no action is required.

   • To set a static IPv6 address, network mask, default gateway, and DNS server to the team0 connection, enter:

     # nmcli connection modify team0 ipv6.addresses '2001:db8:1::1/64' ipv6.gateway '2001:db8:1::fffe' ipv6.dns '2001:db8:1::fffd' ipv6.dns-search 'example.com' ipv6.method manual

7. Activate the connection:

   # nmcli connection up team0

Procedure

1. Select the Networking tab in the navigation on the left side of the screen.
2. Click Add team in the Interfaces section.
3. Enter the name of the team device you want to create.
4. Select the interfaces that should be ports of the team.

5. Select the runner of the team.

   If you select Load balancing or 802.3ad LACP, the web console shows the additional field Balancer.

6. Set the link watcher:

   • If you select Ethtool, additionally, set a link up and link down delay.
   • If you set ARP ping or NSNA ping, additionally, set a ping interval and ping target.
   
7. Click Apply.

8. By default, the team uses a dynamic IP address. If you want to set a static IP address:

   1. Click the name of the team in the Interfaces section.
   2. Click Edit next to the protocol you want to configure.
   3. Select Manual next to Addresses, and enter the IP address, prefix, and default gateway.
   4. In the DNS section, click the + button, and enter the IP address of the DNS server. Repeat this step to set multiple DNS servers.
   5. In the DNS search domains section, click the + button, and enter the search domain.

   6. If the interface requires static routes, configure them in the Routes section.

      
   7. Click Apply

Verification

1. Select the Networking tab in the navigation on the left side of the screen, and check if there is incoming and outgoing traffic on the interface.

   

2. Display the status of the team:

   # teamdctl team0 state
   setup:
     runner: activebackup
   ports:
     enp7s0
       link watches:
         link summary: up
         instance[link_watch_0]:
           name: ethtool
           link: up
           down count: 0
     enp8s0
       link watches:
         link summary: up
         instance[link_watch_0]:
           name: ethtool
           link: up
           down count: 0
   runner:
     active port: enp7s0

   In this example, both ports are up.

Procedure

1. Open a terminal, and enter nm-connection-editor:

   $ nm-connection-editor

2. Click the + button to add a new connection.
3. Select the Team connection type, and click Create.

4. On the Team tab:

   1. Optional: Set the name of the team interface in the Interface name field.

   2. Click the Add button to add a new connection profile for a network interface and adding the profile as a port to the team.

      1. Select the connection type of the interface. For example, select Ethernet for a wired connection.
      2. Optional: Set a connection name for the port.
      3. If you create a connection profile for an Ethernet device, open the Ethernet tab, and select in the Device field the network interface you want to add as a port to the team. If you selected a different device type, configure it accordingly. Note that you can only use Ethernet interfaces in a team that are not assigned to any connection.
      4. Click Save.

   3. Repeat the previous step for each interface you want to add to the team.

      

   4. Click the Advanced button to set advanced options to the team connection.

      1. On the Runner tab, select the runner.
      2. On the Link Watcher tab, set the link watcher and its optional settings.
      3. Click OK.

5. Configure the IP address settings on both the IPv4 Settings and IPv6 Settings tabs:

   • To use this bridge device as a port of other devices, set the Method field to Disabled.
   • To use DHCP, leave the Method field at its default, Automatic (DHCP).

   • To use static IP settings, set the Method field to Manual and fill the fields accordingly:

     

6. Click Save.
7. Close nm-connection-editor.

Procedure

1. Display the network interfaces:

   # nmcli device status
   DEVICE   TYPE      STATE         CONNECTION
   enp1s0   ethernet  disconnected  enp1s0
   bridge0  bridge    connected     bridge0
   bond0    bond      connected     bond0
   ...

2. Create the VLAN interface. For example, to create a VLAN interface named vlan10 that uses enp1s0 as its parent interface and that tags packets with VLAN ID 10, enter:

   # nmcli connection add type vlan con-name vlan10 ifname vlan10 vlan.parent enp1s0 vlan.id 10

   Note that the VLAN must be within the range from 0 to 4094.

3. By default, the VLAN connection inherits the maximum transmission unit (MTU) from the parent interface. Optionally, set a different MTU value:

   # nmcli connection modify vlan10 ethernet.mtu 2000

4. Configure the IPv4 settings:

   • To use this VLAN device as a port of other devices, enter:

     # nmcli connection modify vlan10 ipv4.method disabled

   • To use DHCP, no action is required.

   • To set a static IPv4 address, network mask, default gateway, and DNS server to the vlan10 connection, enter:

     # nmcli connection modify vlan10 ipv4.addresses '192.0.2.1/24' ipv4.gateway '192.0.2.254' ipv4.dns '192.0.2.253' ipv4.method manual

5. Configure the IPv6 settings:

   • To use this VLAN device as a port of other devices, enter:

     # nmcli connection modify vlan10 ipv6.method disabled

   • To use DHCP, no action is required.

   • To set a static IPv6 address, network mask, default gateway, and DNS server to the vlan10 connection, enter:

     # nmcli connection modify vlan10 ipv6.addresses '2001:db8:1::1/32' ipv6.gateway '2001:db8:1::fffe' ipv6.dns '2001:db8:1::fffd' ipv6.method manual

6. Activate the connection:

   # nmcli connection up vlan10

Procedure

1. Select the Networking tab in the navigation on the left side of the screen.
2. Click Add VLAN in the Interfaces section.
3. Select the parent device.
4. Enter the VLAN ID.

5. Enter the name of the VLAN device or keep the automatically-generated name.

   
6. Click Apply.

7. By default, the VLAN device uses a dynamic IP address. If you want to set a static IP address:

   1. Click the name of the VLAN device in the Interfaces section.
   2. Click Edit next to the protocol you want to configure.
   3. Select Manual next to Addresses, and enter the IP address, prefix, and default gateway.
   4. In the DNS section, click the + button, and enter the IP address of the DNS server. Repeat this step to set multiple DNS servers.
   5. In the DNS search domains section, click the + button, and enter the search domain.

   6. If the interface requires static routes, configure them in the Routes section.

      
   7. Click Apply

Procedure

1. If you do not know the network device name on which you want configure VLAN tagging, display the available devices:

   # nmcli device status
   DEVICE     TYPE      STATE                   CONNECTION
   enp1s0     ethernet  unavailable             --
   ...

2. Start nmtui:

   # nmtui

3. Select Edit a connection, and press Enter.
4. Press the Add button.
5. Select VLAN from the list of network types, and press Enter.
6. Optional: Enter a name for the NetworkManager profile to be created.
7. Enter the VLAN device name to be created into the Device field.
8. Enter the name of the device on which you want to configure VLAN tagging into the Parent field.
9. Enter the VLAN ID. The ID must be within the range from 0 to 4094.

10. Depending on your environment, configure the IP address settings in the IPv4 configuration and IPv6 configuration areas accordingly. For this, press the Automatic button, and select:

    • Disabled, if this VLAN device does not require an IP address or you want to use it as a port of other devices.
    • Automatic, if a DHCP server dynamically assigns an IP address to the VLAN device.

    • Manual, if the network requires static IP address settings. In this case, you must fill further fields:

      1. Press the Show button next to the protocol you want to configure to display additional fields.

      2. Press the Add button next to Addresses, and enter the IP address and the subnet mask in Classless Inter-Domain Routing (CIDR) format.

         If you do not specify a subnet mask, NetworkManager sets a /32 subnet mask for IPv4 addresses and /64 for IPv6 addresses.

      3. Enter the address of the default gateway.
      4. Press the Add button next to DNS servers, and enter the DNS server address.
      5. Press the Add button next to Search domains, and enter the DNS search domain.

    Figure 5.1. Example of a VLAN connection with static IP address settings

    
11. Press the OK button to create and automatically activate the new connection.
12. Press the Back button to return to the main menu.
13. Select Quit, and press Enter to close the nmtui application.

Procedure

1. Open a terminal, and enter nm-connection-editor:

   $ nm-connection-editor

2. Click the + button to add a new connection.
3. Select the VLAN connection type, and click Create.

4. On the VLAN tab:

   1. Select the parent interface.
   2. Select the VLAN id. Note that the VLAN must be within the range from 0 to 4094.
   3. By default, the VLAN connection inherits the maximum transmission unit (MTU) from the parent interface. Optionally, set a different MTU value.

   4. Optionally, set the name of the VLAN interface and further VLAN-specific options.

      

5. Configure the IP address settings on both the IPv4 Settings and IPv6 Settings tabs:

   • To use this bridge device as a port of other devices, set the Method field to Disabled.
   • To use DHCP, leave the Method field at its default, Automatic (DHCP).

   • To use static IP settings, set the Method field to Manual and fill the fields accordingly:

     

6. Click Save.
7. Close nm-connection-editor.

Verification

1. Verify the settings:

   # ip -d addr show vlan10
   4: vlan10@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
       link/ether 52:54:00:d5:e0:fb brd ff:ff:ff:ff:ff:ff promiscuity 0
       vlan protocol 802.1Q id 10 <REORDER_HDR> numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535
       inet 192.0.2.1/24 brd 192.0.2.255 scope global noprefixroute vlan10
          valid_lft forever preferred_lft forever
       inet6 2001:db8:1::1/32 scope global noprefixroute
          valid_lft forever preferred_lft forever
       inet6 fe80::8dd7:9030:6f8e:89e6/64 scope link noprefixroute
          valid_lft forever preferred_lft forever

Procedure

1. Create a YAML file, for example ~/create-vlan.yml, with the following contents:

   ---
   interfaces:
   - name: vlan10
     type: vlan
     state: up
     ipv4:
       enabled: true
       address:
       - ip: 192.0.2.1
         prefix-length: 24
       dhcp: false
     ipv6:
       enabled: true
       address:
       - ip: 2001:db8:1::1
         prefix-length: 64
       autoconf: false
       dhcp: false
     vlan:
       base-iface: enp1s0
       id: 10
   - name: enp1s0
     type: ethernet
     state: up
   
   routes:
     config:
     - destination: 0.0.0.0/0
       next-hop-address: 192.0.2.254
       next-hop-interface: vlan10
     - destination: ::/0
       next-hop-address: 2001:db8:1::fffe
       next-hop-interface: vlan10
   
   dns-resolver:
     config:
       search:
       - example.com
       server:
       - 192.0.2.200
       - 2001:db8:1::ffbb

2. Apply the settings to the system:

   # nmstatectl apply ~/create-vlan.yml

Verification

1. Display the status of the devices and connections:

   # nmcli device status
   DEVICE      TYPE      STATE      CONNECTION
   vlan10      vlan      connected  vlan10

2. Display all settings of the connection profile:

   # nmcli connection show vlan10
   connection.id:              vlan10
   connection.uuid:            1722970f-788e-4f81-bd7d-a86bf21c9df5
   connection.stable-id:       --
   connection.type:            vlan
   connection.interface-name:  vlan10
   ...

3. Display the connection settings in YAML format:

   # nmstatectl show vlan0

Procedure

1. Create a playbook file, for example ~/vlan-ethernet.yml, with the following content:

   ---
   - name: Configure the network
     hosts: managed-node-01.example.com
     tasks:
     - name: Configure a VLAN that uses an Ethernet connection
       include_role:
         name: rhel-system-roles.network
   
       vars:
         network_connections:
           # Add an Ethernet profile for the underlying device of the VLAN
           - name: enp1s0
             type: ethernet
             interface_name: enp1s0
             autoconnect: yes
             state: up
             ip:
               dhcp4: no
               auto6: no
   
           # Define the VLAN profile
           - name: enp1s0.10
             type: vlan
             ip:
               address:
                 - "192.0.2.1/24"
                 - "2001:db8:1::1/64"
               gateway4: 192.0.2.254
               gateway6: 2001:db8:1::fffe
               dns:
                 - 192.0.2.200
                 - 2001:db8:1::ffbb
               dns_search:
                 - example.com
             vlan_id: 10
             parent: enp1s0
             state: up

   The parent attribute in the VLAN profile configures the VLAN to operate on top of the enp1s0 device.

2. Run the playbook:

   # ansible-playbook ~/vlan-ethernet.yml

Procedure

1. Create a bridge interface:

   # nmcli connection add type bridge con-name bridge0 ifname bridge0

   This command creates a bridge named bridge0, enter:

2. Display the network interfaces, and note the names of the interfaces you want to add to the bridge:

   # nmcli device status
   DEVICE  TYPE      STATE         CONNECTION
   enp7s0  ethernet  disconnected  --
   enp8s0  ethernet  disconnected  --
   bond0   bond      connected     bond0
   bond1   bond      connected     bond1
   ...

   In this example:

   • enp7s0 and enp8s0 are not configured. To use these devices as ports, add connection profiles in the next step.
   • bond0 and bond1 have existing connection profiles. To use these devices as ports, modify their profiles in the next step.

3. Assign the interfaces to the bridge.

   1. If the interfaces you want to assign to the bridge are not configured, create new connection profiles for them:

      # nmcli connection add type ethernet slave-type bridge con-name bridge0-port1 ifname enp7s0 master bridge0
      # nmcli connection add type ethernet slave-type bridge con-name bridge0-port2 ifname enp8s0 master bridge0

      These commands create profiles for enp7s0 and enp8s0, and add them to the bridge0 connection.

   2. If you want to assign an existing connection profile to the bridge:

      1. Set the master parameter of these connections to bridge0:

         # nmcli connection modify bond0 master bridge0
         # nmcli connection modify bond1 master bridge0

         These commands assign the existing connection profiles named bond0 and bond1 to the bridge0 connection.

      2. Reactivate the connections:

         # nmcli connection up bond0
         # nmcli connection up bond1

4. Configure the IPv4 settings:

   • To use this bridge device as a port of other devices, enter:

     # nmcli connection modify bridge0 ipv4.method disabled

   • To use DHCP, no action is required.

   • To set a static IPv4 address, network mask, default gateway, and DNS server to the bridge0 connection, enter:

     # nmcli connection modify bridge0 ipv4.addresses '192.0.2.1/24' ipv4.gateway '192.0.2.254' ipv4.dns '192.0.2.253' ipv4.dns-search 'example.com' ipv4.method manual

5. Configure the IPv6 settings:

   • To use this bridge device as a port of other devices, enter:

     # nmcli connection modify bridge0 ipv6.method disabled

   • To use DHCP, no action is required.

   • To set a static IPv6 address, network mask, default gateway, and DNS server to the bridge0 connection, enter:

     # nmcli connection modify bridge0 ipv6.addresses '2001:db8:1::1/64' ipv6.gateway '2001:db8:1::fffe' ipv6.dns '2001:db8:1::fffd' ipv6.dns-search 'example.com' ipv6.method manual

6. Optional: Configure further properties of the bridge. For example, to set the Spanning Tree Protocol (STP) priority of bridge0 to 16384, enter:

   # nmcli connection modify bridge0 bridge.priority '16384'

   By default, STP is enabled.

7. Activate the connection:

   # nmcli connection up bridge0

8. Verify that the ports are connected, and the CONNECTION column displays the port’s connection name:

   # nmcli device
   DEVICE   TYPE      STATE      CONNECTION
   ...
   enp7s0   ethernet  connected  bridge0-port1
   enp8s0   ethernet  connected  bridge0-port2

   When you activate any port of the connection, NetworkManager also activates the bridge, but not the other ports of it. You can configure that Red Hat Enterprise Linux enables all ports automatically when the bridge is enabled:

   1. Enable the connection.autoconnect-slaves parameter of the bridge connection:

      # nmcli connection modify bridge0 connection.autoconnect-slaves 1

   2. Reactivate the bridge:

      # nmcli connection up bridge0

Procedure

1. Select the Networking tab in the navigation on the left side of the screen.
2. Click Add bridge in the Interfaces section.
3. Enter the name of the bridge device you want to create.
4. Select the interfaces that should be ports of the bridge.

5. Optional: Enable the Spanning tree protocol (STP) feature to avoid bridge loops and broadcast radiation.

   
6. Click Apply.

7. By default, the bridge uses a dynamic IP address. If you want to set a static IP address:

   1. Click the name of the bridge in the Interfaces section.
   2. Click Edit next to the protocol you want to configure.
   3. Select Manual next to Addresses, and enter the IP address, prefix, and default gateway.
   4. In the DNS section, click the + button, and enter the IP address of the DNS server. Repeat this step to set multiple DNS servers.
   5. In the DNS search domains section, click the + button, and enter the search domain.

   6. If the interface requires static routes, configure them in the Routes section.

      
   7. Click Apply

Verification

1. Select the Networking tab in the navigation on the left side of the screen, and check if there is incoming and outgoing traffic on the interface:

   

Procedure

1. If you do not know the network device names on which you want configure a network bridge, display the available devices:

   # nmcli device status
   DEVICE     TYPE      STATE                   CONNECTION
   enp7s0     ethernet  unavailable             --
   enp8s0     ethernet  unavailable             --
   ...

2. Start nmtui:

   # nmtui

3. Select Edit a connection, and press Enter.
4. Press the Add button.
5. Select Bridge from the list of network types, and press Enter.
6. Optional: Enter a name for the NetworkManager profile to be created.
7. Enter the bridge device name to be created into the Device field.

8. Add ports to the bridge to be created:

   1. Press the Add button next to the Slaves list.
   2. Select the type of the interface you want to add as port to the bridge, for example, Ethernet.
   3. Optional: Enter a name for the NetworkManager profile to be created for this bridge port.
   4. Enter the port’s device name into the Device field.

   5. Press the OK button to return to the window with the bridge settings.

      Figure 6.1. Adding an Ethernet device as port to a bridge

      
   6. Repeat these steps to add more ports to the bridge.

9. Depending on your environment, configure the IP address settings in the IPv4 configuration and IPv6 configuration areas accordingly. For this, press the Automatic button, and select:

   • Disabled, if the bridge does not require an IP address.
   • Automatic, if a DHCP server dynamically assigns an IP address to the bridge.

   • Manual, if the network requires static IP address settings. In this case, you must fill further fields:

     1. Press the Show button next to the protocol you want to configure to display additional fields.

     2. Press the Add button next to Addresses, and enter the IP address and the subnet mask in Classless Inter-Domain Routing (CIDR) format.

        If you do not specify a subnet mask, NetworkManager sets a /32 subnet mask for IPv4 addresses and /64 for IPv6 addresses.

     3. Enter the address of the default gateway.
     4. Press the Add button next to DNS servers, and enter the DNS server address.
     5. Press the Add button next to Search domains, and enter the DNS search domain.

   Figure 6.2. Example of a bridge connection without IP address settings

   
10. Press the OK button to create and automatically activate the new connection.
11. Press the Back button to return to the main menu.
12. Select Quit, and press Enter to close the nmtui application.

Verification

1. Use the ip utility to display the link status of Ethernet devices that are ports of a specific bridge:

   # ip link show master bridge0
   3: enp7s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master bridge0 state UP mode DEFAULT group default qlen 1000
       link/ether 52:54:00:62:61:0e brd ff:ff:ff:ff:ff:ff
   4: enp8s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master bridge0 state UP mode DEFAULT group default qlen 1000
       link/ether 52:54:00:9e:f1:ce brd ff:ff:ff:ff:ff:ff

2. Use the bridge utility to display the status of Ethernet devices that are ports of any bridge device:

   # bridge link show
   3: enp7s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master bridge0 state forwarding priority 32 cost 100
   4: enp8s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master bridge0 state listening priority 32 cost 100
   ...

   To display the status for a specific Ethernet device, use the bridge link show dev ethernet_device_name command.

Procedure

1. Open a terminal, and enter nm-connection-editor:

   $ nm-connection-editor

2. Click the + button to add a new connection.
3. Select the Bridge connection type, and click Create.

4. On the Bridge tab:

   1. Optional: Set the name of the bridge interface in the Interface name field.

   2. Click the Add button to create a new connection profile for a network interface and adding the profile as a port to the bridge.

      1. Select the connection type of the interface. For example, select Ethernet for a wired connection.
      2. Optionally, set a connection name for the port device.
      3. If you create a connection profile for an Ethernet device, open the Ethernet tab, and select in the Device field the network interface you want to add as a port to the bridge. If you selected a different device type, configure it accordingly.
      4. Click Save.

   3. Repeat the previous step for each interface you want to add to the bridge.

      

5. Optional: Configure further bridge settings, such as Spanning Tree Protocol (STP) options.

6. Configure the IP address settings on both the IPv4 Settings and IPv6 Settings tabs:

   • To use this bridge device as a port of other devices, set the Method field to Disabled.
   • To use DHCP, leave the Method field at its default, Automatic (DHCP).

   • To use static IP settings, set the Method field to Manual and fill the fields accordingly:

     

7. Click Save.
8. Close nm-connection-editor.

Procedure

1. Create a YAML file, for example ~/create-bridge.yml, with the following contents:

   ---
   interfaces:
   - name: bridge0
     type: linux-bridge
     state: up
     ipv4:
       enabled: true
       address:
       - ip: 192.0.2.1
         prefix-length: 24
       dhcp: false
     ipv6:
       enabled: true
       address:
       - ip: 2001:db8:1::1
         prefix-length: 64
       autoconf: false
       dhcp: false
     bridge:
       options:
         stp:
           enabled: true
       port:
         - name: enp1s0
         - name: enp7s0
   - name: enp1s0
     type: ethernet
     state: up
   - name: enp7s0
     type: ethernet
     state: up
   
   routes:
     config:
     - destination: 0.0.0.0/0
       next-hop-address: 192.0.2.254
       next-hop-interface: bridge0
     - destination: ::/0
       next-hop-address: 2001:db8:1::fffe
       next-hop-interface: bridge0
   dns-resolver:
     config:
       search:
       - example.com
       server:
       - 192.0.2.200
       - 2001:db8:1::ffbb

2. Apply the settings to the system:

   # nmstatectl apply ~/create-bridge.yml

Verification

1. Display the status of the devices and connections:

   # nmcli device status
   DEVICE      TYPE      STATE      CONNECTION
   bridge0     bridge    connected  bridge0

2. Display all settings of the connection profile:

   # nmcli connection show bridge0
   connection.id:              bridge0
   connection.uuid:            e2cc9206-75a2-4622-89cf-1252926060a9
   connection.stable-id:       --
   connection.type:            bridge
   connection.interface-name:  bridge0
   ...

3. Display the connection settings in YAML format:

   # nmstatectl show bridge0

Procedure

1. Create a playbook file, for example ~/bridge-ethernet.yml, with the following content:

   ---
   - name: Configure the network
     hosts: managed-node-01.example.com
     tasks:
     - name: Configure a network bridge that uses two Ethernet ports
       include_role:
         name: rhel-system-roles.network
   
       vars:
         network_connections:
           # Define the bridge profile
           - name: bridge0
             type: bridge
             interface_name: bridge0
             ip:
               address:
                 - "192.0.2.1/24"
                 - "2001:db8:1::1/64"
               gateway4: 192.0.2.254
               gateway6: 2001:db8:1::fffe
               dns:
                 - 192.0.2.200
                 - 2001:db8:1::ffbb
               dns_search:
                 - example.com
             state: up
   
           # Add an Ethernet profile to the bridge
           - name: bridge0-port1
             interface_name: enp7s0
             type: ethernet
             controller: bridge0
             port_type: bridge
             state: up
   
           # Add a second Ethernet profile to the bridge
           - name: bridge0-port2
             interface_name: enp8s0
             type: ethernet
             controller: bridge0
             port_type: bridge
             state: up

2. Run the playbook:

   # ansible-playbook ~/bridge-ethernet.yml

Procedure

1. Press the Super key, type Settings, and press Enter to open the control-center application.
2. Select the Network entry on the left.
3. Click the + icon.
4. Select VPN.

5. Select the Identity menu entry to see the basic configuration options:

   General

   Gateway — The name or IP address of the remote VPN gateway.

   Authentication

   Type

   • IKEv2 (Certificate)- client is authenticated by certificate. It is more secure (default).

   • IKEv1 (XAUTH) - client is authenticated by user name and password, or a pre-shared key (PSK).

     The following configuration settings are available under the Advanced section:

     Figure 7.1. Advanced options of a VPN connection

     
     Warning

     When configuring an IPsec-based VPN connection using the gnome-control-center application, the Advanced dialog displays the configuration, but it does not allow any changes. As a consequence, users cannot change any advanced IPsec options. Use the nm-connection-editor or nmcli tools instead to perform configuration of the advanced properties.

     Identification

   • Domain — If required, enter the Domain Name.

     Security

   • Phase1 Algorithms — corresponds to the ike Libreswan parameter — enter the algorithms to be used to authenticate and set up an encrypted channel.

   • Phase2 Algorithms — corresponds to the esp Libreswan parameter — enter the algorithms to be used for the IPsec negotiations.

     Check the Disable PFS field to turn off Perfect Forward Secrecy (PFS) to ensure compatibility with old servers that do not support PFS.

   • Phase1 Lifetime — corresponds to the ikelifetime Libreswan parameter — how long the key used to encrypt the traffic will be valid.

   • Phase2 Lifetime — corresponds to the salifetime Libreswan parameter — how long a particular instance of a connection should last before expiring.

     Note that the encryption key should be changed from time to time for security reasons.

   • Remote network — corresponds to the rightsubnet Libreswan parameter — the destination private remote network that should be reached through the VPN.

     Check the narrowing field to enable narrowing. Note that it is only effective in IKEv2 negotiation.

   • Enable fragmentation — corresponds to the fragmentation Libreswan parameter — whether or not to allow IKE fragmentation. Valid values are yes (default) or no.
   • Enable Mobike — corresponds to the mobike Libreswan parameter — whether to allow Mobility and Multihoming Protocol (MOBIKE, RFC 4555) to enable a connection to migrate its endpoint without needing to restart the connection from scratch. This is used on mobile devices that switch between wired, wireless, or mobile data connections. The values are no (default) or yes.

6. Select the IPv4 menu entry:

   IPv4 Method

   • Automatic (DHCP) — Choose this option if the network you are connecting to uses a DHCP server to assign dynamic IP addresses.
   • Link-Local Only — Choose this option if the network you are connecting to does not have a DHCP server and you do not want to assign IP addresses manually. Random addresses will be assigned as per RFC 3927 with prefix 169.254/16.
   • Manual — Choose this option if you want to assign IP addresses manually.

   • Disable — IPv4 is disabled for this connection.

     DNS

     In the DNS section, when Automatic is ON, switch it to OFF to enter the IP address of a DNS server you want to use separating the IPs by comma.

     Routes

     Note that in the Routes section, when Automatic is ON, routes from DHCP are used, but you can also add additional static routes. When OFF, only static routes are used.

   • Address — Enter the IP address of a remote network or host.
   • Netmask — The netmask or prefix length of the IP address entered above.
   • Gateway — The IP address of the gateway leading to the remote network or host entered above.

   • Metric — A network cost, a preference value to give to this route. Lower values will be preferred over higher values.

     Use this connection only for resources on its network

     Select this check box to prevent the connection from becoming the default route. Selecting this option means that only traffic specifically destined for routes learned automatically over the connection or entered here manually is routed over the connection.

7. To configure IPv6 settings in a VPN connection, select the IPv6 menu entry:

   IPv6 Method

   • Automatic — Choose this option to use IPv6 Stateless Address AutoConfiguration (SLAAC) to create an automatic, stateless configuration based on the hardware address and Router Advertisements (RA).
   • Automatic, DHCP only — Choose this option to not use RA, but request information from DHCPv6 directly to create a stateful configuration.
   • Link-Local Only — Choose this option if the network you are connecting to does not have a DHCP server and you do not want to assign IP addresses manually. Random addresses will be assigned as per RFC 4862 with prefix FE80::0.
   • Manual — Choose this option if you want to assign IP addresses manually.

   • Disable — IPv6 is disabled for this connection.

     Note that DNS, Routes, Use this connection only for resources on its network are common to IPv4 settings.

8. Once you have finished editing the VPN connection, click the Add button to customize the configuration or the Apply button to save it for the existing one.
9. Switch the profile to ON to active the VPN connection.

Procedure

1. Edit the Libreswan configuration file in the /etc/ipsec.d/ directory of the connection that should use automatic detection of ESP hardware offload support.
2. Ensure the nic-offload parameter is not set in the connection’s settings.

3. If you removed nic-offload, restart the ipsec service:

   # systemctl restart ipsec

1. Display the tx_ipsec and rx_ipsec counters of the Ethernet device the IPsec connection uses:

   # ethtool -S enp1s0 | egrep "_ipsec"
        tx_ipsec: 10
        rx_ipsec: 10

2. Send traffic through the IPsec tunnel. For example, ping a remote IP address:

   # ping -c 5 remote_ip_address

3. Display the tx_ipsec and rx_ipsec counters of the Ethernet device again:

   # ethtool -S enp1s0 | egrep "_ipsec"
        tx_ipsec: 15
        rx_ipsec: 15

   If the counter values have increased, ESP hardware offload works.

Procedure

1. Enable ESP hardware offload support on the network bond:

   # nmcli connection modify bond0 ethtool.feature-esp-hw-offload on

   This command enables ESP hardware offload support on the bond0 connection.

2. Reactivate the bond0 connection:

   # nmcli connection up bond0

3. Edit the Libreswan configuration file in the /etc/ipsec.d/ directory of the connection that should use ESP hardware offload, and append the nic-offload=yes statement to the connection entry:

   conn example
       ...
       nic-offload=yes

4. Restart the ipsec service:

   # systemctl restart ipsec

Verification

1. Display the active port of the bond:

   # grep "Currently Active Slave" /proc/net/bonding/bond0
   Currently Active Slave: enp1s0

2. Display the tx_ipsec and rx_ipsec counters of the active port:

   # ethtool -S enp1s0 | egrep "_ipsec"
        tx_ipsec: 10
        rx_ipsec: 10

3. Send traffic through the IPsec tunnel. For example, ping a remote IP address:

   # ping -c 5 remote_ip_address

4. Display the tx_ipsec and rx_ipsec counters of the active port again:

   # ethtool -S enp1s0 | egrep "_ipsec"
        tx_ipsec: 15
        rx_ipsec: 15

   If the counter values have increased, ESP hardware offload works.

Procedure

1. On the RHEL router in network A:

   1. Create an IPIP tunnel interface named tun0:

      # nmcli connection add type ip-tunnel ip-tunnel.mode ipip con-name tun0 ifname tun0 remote 198.51.100.5 local 203.0.113.10

      The remote and local parameters set the public IP addresses of the remote and the local routers.

   2. Set the IPv4 address to the tun0 device:

      # nmcli connection modify tun0 ipv4.addresses '10.0.1.1/30'

      Note that a /30 subnet with two usable IP addresses is sufficient for the tunnel.

   3. Configure the tun0 connection to use a manual IPv4 configuration:

      # nmcli connection modify tun0 ipv4.method manual

   4. Add a static route that routes traffic to the 172.16.0.0/24 network to the tunnel IP on router B:

      # nmcli connection modify tun0 +ipv4.routes "172.16.0.0/24 10.0.1.2"

   5. Enable the tun0 connection.

      # nmcli connection up tun0

   6. Enable packet forwarding:

      # echo "net.ipv4.ip_forward=1" > /etc/sysctl.d/95-IPv4-forwarding.conf
      # sysctl -p /etc/sysctl.d/95-IPv4-forwarding.conf

2. On the RHEL router in network B:

   1. Create an IPIP tunnel interface named tun0:

      # nmcli connection add type ip-tunnel ip-tunnel.mode ipip con-name tun0 ifname tun0 remote 203.0.113.10 local 198.51.100.5

      The remote and local parameters set the public IP addresses of the remote and local routers.

   2. Set the IPv4 address to the tun0 device:

      # nmcli connection modify tun0 ipv4.addresses '10.0.1.2/30'

   3. Configure the tun0 connection to use a manual IPv4 configuration:

      # nmcli connection modify tun0 ipv4.method manual

   4. Add a static route that routes traffic to the 192.0.2.0/24 network to the tunnel IP on router A:

      # nmcli connection modify tun0 +ipv4.routes "192.0.2.0/24 10.0.1.1"

   5. Enable the tun0 connection.

      # nmcli connection up tun0

   6. Enable packet forwarding:

      # echo "net.ipv4.ip_forward=1" > /etc/sysctl.d/95-IPv4-forwarding.conf
      # sysctl -p /etc/sysctl.d/95-IPv4-forwarding.conf

Procedure

1. On the RHEL router in network A:

   1. Create a GRE tunnel interface named gre1:

      # nmcli connection add type ip-tunnel ip-tunnel.mode gre con-name gre1 ifname gre1 remote 198.51.100.5 local 203.0.113.10

      The remote and local parameters set the public IP addresses of the remote and the local routers.

   2. Set the IPv4 address to the gre1 device:

      # nmcli connection modify gre1 ipv4.addresses '10.0.1.1/30'

      Note that a /30 subnet with two usable IP addresses is sufficient for the tunnel.

   3. Configure the gre1 connection to use a manual IPv4 configuration:

      # nmcli connection modify gre1 ipv4.method manual

   4. Add a static route that routes traffic to the 172.16.0.0/24 network to the tunnel IP on router B:

      # nmcli connection modify gre1 +ipv4.routes "172.16.0.0/24 10.0.1.2"

   5. Enable the gre1 connection.

      # nmcli connection up gre1

   6. Enable packet forwarding:

      # echo "net.ipv4.ip_forward=1" > /etc/sysctl.d/95-IPv4-forwarding.conf
      # sysctl -p /etc/sysctl.d/95-IPv4-forwarding.conf

2. On the RHEL router in network B:

   1. Create a GRE tunnel interface named gre1:

      # nmcli connection add type ip-tunnel ip-tunnel.mode gre con-name gre1 ifname gre1 remote 203.0.113.10 local 198.51.100.5

      The remote and local parameters set the public IP addresses of the remote and the local routers.

   2. Set the IPv4 address to the gre1 device:

      # nmcli connection modify gre1 ipv4.addresses '10.0.1.2/30'

   3. Configure the gre1 connection to use a manual IPv4 configuration:

      # nmcli connection modify gre1 ipv4.method manual

   4. Add a static route that routes traffic to the 192.0.2.0/24 network to the tunnel IP on router A:

      # nmcli connection modify gre1 +ipv4.routes "192.0.2.0/24 10.0.1.1"

   5. Enable the gre1 connection.

      # nmcli connection up gre1

   6. Enable packet forwarding:

      # echo "net.ipv4.ip_forward=1" > /etc/sysctl.d/95-IPv4-forwarding.conf
      # sysctl -p /etc/sysctl.d/95-IPv4-forwarding.conf

Verification

1. From each RHEL router, ping the IP address of the internal interface of the other router:

   1. On Router A, ping 172.16.0.1:

      # ping 172.16.0.1

   2. On Router B, ping 192.0.2.1:

      # ping 192.0.2.1

Procedure

1. On the RHEL router in network A:

   1. Create a bridge interface named bridge0:

      # nmcli connection add type bridge con-name bridge0 ifname bridge0

   2. Configure the IP settings of the bridge:

      # nmcli connection modify bridge0 ipv4.addresses '192.0.2.1/24'
      # nmcli connection modify bridge0 ipv4.method manual

   3. Add a new connection profile for the interface that is connected to local network to the bridge:

      # nmcli connection add type ethernet slave-type bridge con-name bridge0-port1 ifname enp1s0 master bridge0

   4. Add a new connection profile for the GRETAP tunnel interface to the bridge:

      # nmcli connection add type ip-tunnel ip-tunnel.mode gretap slave-type bridge con-name bridge0-port2 ifname gretap1 remote 198.51.100.5 local 203.0.113.10 master bridge0

      The remote and local parameters set the public IP addresses of the remote and the local routers.

   5. Optional: Disable the Spanning Tree Protocol (STP) if you do not need it:

      # nmcli connection modify bridge0 bridge.stp no

      By default, STP is enabled and causes a delay before you can use the connection.

   6. Configure that activating the bridge0 connection automatically activates the ports of the bridge:

      # nmcli connection modify bridge0 connection.autoconnect-slaves 1

   7. Active the bridge0 connection:

      # nmcli connection up bridge0

2. On the RHEL router in network B:

   1. Create a bridge interface named bridge0:

      # nmcli connection add type bridge con-name bridge0 ifname bridge0

   2. Configure the IP settings of the bridge:

      # nmcli connection modify bridge0 ipv4.addresses '192.0.2.2/24'
      # nmcli connection modify bridge0 ipv4.method manual

   3. Add a new connection profile for the interface that is connected to local network to the bridge:

      # nmcli connection add type ethernet slave-type bridge con-name bridge0-port1 ifname enp1s0 master bridge0

   4. Add a new connection profile for the GRETAP tunnel interface to the bridge:

      # nmcli connection add type ip-tunnel ip-tunnel.mode gretap slave-type bridge con-name bridge0-port2 ifname gretap1 remote 203.0.113.10 local 198.51.100.5 master bridge0

      The remote and local parameters set the public IP addresses of the remote and the local routers.

   5. Optional: Disable the Spanning Tree Protocol (STP) if you do not need it:

      # nmcli connection modify bridge0 bridge.stp no

   6. Configure that activating the bridge0 connection automatically activates the ports of the bridge:

      # nmcli connection modify bridge0 connection.autoconnect-slaves 1

   7. Active the bridge0 connection:

      # nmcli connection up bridge0

Verification

1. On both routers, verify that the enp1s0 and gretap1 connections are connected and that the CONNECTION column displays the connection name of the port:

   # nmcli device
   nmcli device
   DEVICE   TYPE      STATE      CONNECTION
   ...
   bridge0  bridge    connected  bridge0
   enp1s0   ethernet  connected  bridge0-port1
   gretap1  iptunnel  connected  bridge0-port2

2. From each RHEL router, ping the IP address of the internal interface of the other router:

   1. On Router A, ping 192.0.2.2:

      # ping 192.0.2.2

   2. On Router B, ping 192.0.2.1:

      # ping 192.0.2.1

Procedure

1. Add a new Ethernet connection profile to NetworkManager:

   # nmcli connection add con-name Example ifname enp1s0 type ethernet

2. Configure the IPv4 settings:

   # nmcli connection modify Example ipv4.addresses 198.51.100.2/24 ipv4.method manual ipv4.gateway 198.51.100.254 ipv4.dns 198.51.100.200 ipv4.dns-search example.com

   Skip this step if the network uses DHCP.

3. Activate the Example connection:

   # nmcli connection up Example

Verification

1. Display the status of the devices and connections:

   # nmcli device status
   DEVICE      TYPE      STATE      CONNECTION
   enp1s0      ethernet  connected  Example

2. Ping a host in a remote network to verify the IP settings:

   # ping RHEL-host-B.example.com

   Note that you cannot ping the other VM host before you have configured the network on that host as well.

Procedure

1. Create the bridge br0:

   # nmcli connection add type bridge con-name br0 ifname br0 ipv4.method disabled ipv6.method disabled

   This command sets no IPv4 and IPv6 addresses on the bridge device, because this bridge works on layer 2.

2. Create the VXLAN interface and attach it to br0:

   # nmcli connection add type vxlan slave-type bridge con-name br0-vxlan10 ifname vxlan10 id 10 local 198.51.100.2 remote 203.0.113.1 master br0

   This command uses the following settings:

   • id 10: Sets the VXLAN identifier.
   • local 198.51.100.2: Sets the source IP address of outgoing packets.
   • remote 203.0.113.1: Sets the unicast or multicast IP address to use in outgoing packets when the destination link layer address is not known in the VXLAN device forwarding database.
   • master br0: Sets this VXLAN connection to be created as a port in the br0 connection.
   • ipv4.method disabled and ipv6.method disabled: Disables IPv4 and IPv6 on the bridge.

   By default, NetworkManager uses 8472 as the destination port. If the destination port is different, additionally, pass the destination-port <port_number> option to the command.

3. Activate the br0 connection profile:

   # nmcli connection up br0

4. Open port 8472 for incoming UDP connections in the local firewall:

   # firewall-cmd --permanent --add-port=8472/udp
   # firewall-cmd --reload

Procedure

1. Create the ~/vxlan10-bridge.xml file with the following content:

   <network>
    <name>vxlan10-bridge</name>
    <forward mode="bridge" />
    <bridge name="br0" />
   </network>

2. Use the ~/vxlan10-bridge.xml file to create a new virtual network in libvirt:

   # virsh net-define ~/vxlan10-bridge.xml

3. Remove the ~/vxlan10-bridge.xml file:

   # rm ~/vxlan10-bridge.xml

4. Start the vxlan10-bridge virtual network:

   # virsh net-start vxlan10-bridge

5. Configure the vxlan10-bridge virtual network to start automatically when the libvirtd service starts:

   # virsh net-autostart vxlan10-bridge

Verification

1. Display the virtual network interfaces of the VM on the host:

   # virsh domiflist VM_name
    Interface   Type     Source           Model    MAC
   -------------------------------------------------------------------
    vnet1       bridge   vxlan10-bridge   virtio   52:54:00:c5:98:1c

2. Display the interfaces attached to the vxlan10-bridge bridge:

   # ip link show master vxlan10-bridge
   18: vxlan10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UNKNOWN mode DEFAULT group default qlen 1000
       link/ether 2a:53:bd:d5:b3:0a brd ff:ff:ff:ff:ff:ff
   19: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UNKNOWN mode DEFAULT group default qlen 1000
       link/ether 52:54:00:c5:98:1c brd ff:ff:ff:ff:ff:ff

   Note that the libvirtd service dynamically updates the bridge’s configuration. When you start a VM which uses the vxlan10-bridge network, the corresponding vnet* device on the host appears as a port of the bridge.

3. Use address resolution protocol (ARP) requests to verify whether VMs are in the same VXLAN:

   1. Start two or more VMs in the same VXLAN.

   2. Send an ARP request from one VM to the other one:

      # arping -c 1 192.0.2.2
      ARPING 192.0.2.2 from 192.0.2.1 enp1s0
      Unicast reply from 192.0.2.2 [52:54:00:c5:98:1c] 1.450ms
      Sent 1 probe(s) (0 broadcast(s))
      Received 1 response(s) (0 request(s), 0 broadcast(s))

      If the command shows a reply, the VM is in the same layer-2 domain and, in this case in the same VXLAN.

      Install the iputils package to use the arping utility.

Procedure

1. If the wifi radio has been disabled in NetworkManager, enable this feature:

   # nmcli radio wifi on

2. Optional: Display the available wifi networks:

   # nmcli device wifi list
   IN-USE  BSSID              SSID          MODE   CHAN  RATE        SIGNAL  BARS  SECURITY
           00:53:00:2F:3B:08  Office        Infra  44    270 Mbit/s  57      ▂▄▆_  WPA2 WPA3
           00:53:00:15:03:BF  --            Infra  1     130 Mbit/s  48      ▂▄__  WPA2 WPA3

   The service set identifier (SSID) column contains the names of the networks. If the column shows --, the access point of this network does not broadcast an SSID.

3. Connect to the wifi network:

   # nmcli device wifi connect Office --ask
   Password: wifi-password

   If you prefer to set the password in the command instead of entering it interactively, use the password wifi-password option in the command instead of --ask:

   # nmcli device wifi connect Office wifi-password

   Note that, if the network requires static IP addresses, NetworkManager fails to activate the connection at this point. You can configure the IP addresses in later steps.

4. If the network requires static IP addresses:

   1. Configure the IPv4 address settings, for example:

      # nmcli connection modify Office ipv4.method manual ipv4.addresses 192.0.2.1/24 ipv4.gateway 192.0.2.254 ipv4.dns 192.0.2.200 ipv4.dns-search example.com

   2. Configure the IPv6 address settings, for example:

      # nmcli connection modify Office ipv6.method manual ipv6.addresses 2001:db8:1::1/64 ipv6.gateway 2001:db8:1::fffe ipv6.dns 2001:db8:1::ffbb ipv6.dns-search example.com

5. Re-activate the connection:

   # nmcli connection up Office

Verification

1. Display the active connections:

   # nmcli connection show --active
   NAME    ID                                    TYPE  DEVICE
   Office  2501eb7e-7b16-4dc6-97ef-7cc460139a58  wifi  wlp0s20f3

   If the output lists the wifi connection you have created, the connection is active.

2. Ping a hostname or IP address:

   # ping -c 3 example.com

Procedure

1. Open the system menu on the right side of the top bar.
2. Expand the Wi-Fi Not Connected entry.

3. Click Select Network:

   
4. Select the wifi network you want to connect to.
5. Click Connect.
6. If this is the first time you connect to this network, enter the password for the network, and click Connect.

Verification

1. Open the system menu on the right side of the top bar, and verify that the wifi network is connected:

   

   If the network appears in the list, it is connected.

2. Ping a hostname or IP address:

   # ping -c 3 example.com

Procedure

1. Press the Super key, type Wi-Fi, and press Enter.
2. Click on the name of the wifi network you want to connect to.
3. Enter the password for the network, and click Connect.

4. If the network requires additional settings, such as static IP addresses or a security type other than WPA2 Personal:

   1. Click the gear icon next to the network’s name.

   2. Optional: Configure the network profile on the Details tab to not automatically connect.

      If you deactivate this feature, you must always manually connect to the network, for example, by using GNOME settings or the GNOME system menu.

   3. Configure IPv4 settings on the IPv4 tab, and IPv6 settings on the IPv6 tab.

   4. On the Security tab, select the authentication of the network, such as WPA3 Personal, and enter the password.

      Depending on the selected security, the application shows additional fields. Fill them accordingly. For details, ask the administrator of the wifi network.

   5. Click Apply.

Verification

1. Open the system menu on the right side of the top bar, and verify that the wifi network is connected:

   

   If the network appears in the list, it is connected.

2. Ping a hostname or IP address:

   # ping -c 3 example.com

Procedure

1. If you do not know the network device name you want to use in the connection, display the available devices:

   # nmcli device status
   DEVICE     TYPE      STATE                   CONNECTION
   wlp2s0    wifi      unavailable             --
   ...

2. Start nmtui:

   # nmtui

3. Select Edit a connection, and press Enter.
4. Press the Add button.
5. Select Wi-Fi from the list of network types, and press Enter.
6. Optional: Enter a name for the NetworkManager profile to be created.
7. Enter the network device name into the Device field.
8. Enter the name of the Wi-Fi network, the Service Set Identifier (SSID), into the SSID field.
9. Leave the Mode field set to its default, Client.

10. Select the Security field, press Enter, and set the authentication type of the network from the list.

    Depending on the authentication type you have selected, nmtui displays different fields.

11. Fill the authentication type-related fields.

12. If the Wi-Fi network requires static IP addresses:

    1. Press the Automatic button next to the protocol, and select Manual from the displayed list.
    2. Press the Show button next to the protocol you want to configure to display additional fields, and fill them.

13. Press the OK button to create and automatically activate the new connection.

    
14. Press the Back button to return to the main menu.
15. Select Quit, and press Enter to close the nmtui application.

Verification

1. Display the active connections:

   # nmcli connection show --active
   NAME    ID                                    TYPE  DEVICE
   Office  2501eb7e-7b16-4dc6-97ef-7cc460139a58  wifi  wlp0s20f3

   If the output lists the wifi connection you have created, the connection is active.

2. Ping a hostname or IP address:

   # ping -c 3 example.com

Procedure

1. Open a terminal and enter:

   # nm-connection-editor

2. Click the + button to add a new connection.
3. Select the Wi-Fi connection type, and click Create.
4. Optional: Set a name for the connection profile.

5. Optional: Configure the network profile on the General tab to not automatically connect.

   If you deactivate this feature, you must always manually connect to the network, for example, by using GNOME settings or the GNOME system menu.

6. On the Wi-Fi tab, enter the service set identifier (SSID) in the SSID field.

7. On the Wi-Fi Security tab, select the authentication type for the network, such as WPA3 Personal, and enter the password.

   Depending on the selected security, the application shows additional fields. Fill them accordingly. For details, ask the administrator of the wifi network.

8. Configure IPv4 settings on the IPv4 tab, and IPv6 settings on the IPv6 tab.
9. Click Save.
10. Close the Network Connections window.

Verification

1. Open the system menu on the right side of the top bar, and verify that the wifi network is connected:

   

   If the network appears in the list, it is connected.

2. Ping a hostname or IP address:

   # ping -c 3 example.com

Procedure

1. Create a playbook file, for example ~/enable-802.1x.yml, with the following content:

   ---
   - name: Configure a wifi connection with 802.1X authentication
     hosts: managed-node-01.example.com
     tasks:
       - name: Copy client key for 802.1X authentication
         copy:
           src: "/srv/data/client.key"
           dest: "/etc/pki/tls/private/client.key"
           mode: 0400
   
       - name: Copy client certificate for 802.1X authentication
         copy:
           src: "/srv/data/client.crt"
           dest: "/etc/pki/tls/certs/client.crt"
   
       - name: Copy CA certificate for 802.1X authentication
         copy:
           src: "/srv/data/ca.crt"
           dest: "/etc/pki/ca-trust/source/anchors/ca.crt"
   
       - block:
           - import_role:
               name: linux-system-roles.network
             vars:
               network_connections:
                 - name: Configure the Example-wifi profile
                   interface_name: wlp1s0
                   state: up
                   type: wireless
                   autoconnect: yes
                   ip:
                     dhcp4: true
                     auto6: true
                   wireless:
                     ssid: "Example-wifi"
                     key_mgmt: "wpa-eap"
                   ieee802_1x:
                     identity: "user_name"
                     eap: tls
                     private_key: "/etc/pki/tls/client.key"
                     private_key_password: "password"
                     private_key_password_flags: none
                     client_cert: "/etc/pki/tls/client.pem"
                     ca_cert: "/etc/pki/tls/cacert.pem"
                     domain_suffix_match: "example.com"

2. Run the playbook:

   # ansible-playbook ~/enable-802.1x.yml

Procedure

1. Set the wifi security mode to wpa-eap, the Extensible Authentication Protocol (EAP) to peap, the inner authentication protocol to mschapv2, and the user name:

   # nmcli connection modify wlp1s0 wireless-security.key-mgmt wpa-eap 802-1x.eap peap 802-1x.phase2-auth mschapv2 802-1x.identity user_name

   Note that you must set the wireless-security.key-mgmt, 802-1x.eap, 802-1x.phase2-auth, and 802-1x.identity parameters in a single command.

2. Optionally, store the password in the configuration:

   # nmcli connection modify wlp1s0 802-1x.password password

   Important

   By default, NetworkManager stores the password in plain text in the /etc/sysconfig/network-scripts/keys-connection_name file, which is readable only by the root user. However, plain text passwords in a configuration file can be a security risk.

   To increase the security, set the 802-1x.password-flags parameter to 0x1. With this setting, on servers with the GNOME desktop environment or the nm-applet running, NetworkManager retrieves the password from these services. In other cases, NetworkManager prompts for the password.

3. If the client needs to verify the certificate of the authenticator, set the 802-1x.ca-cert parameter in the connection profile to the path of the CA certificate:

   # nmcli connection modify wlp1s0 802-1x.ca-cert /etc/pki/ca-trust/source/anchors/ca.crt

   Note

   For security reasons, Red Hat recommends the certificate of the authenticator to enable clients to validate the identity of the authenticator.

4. Activate the connection profile:

   # nmcli connection up wlp1s0