Chapter 23. Configuring static routes

Procedure

1. Add the static route to the example connection:

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

   To set multiple routes in one step, pass the individual routes comma-separated to the command. For example, to add a route to the 192.0.2.0/24 and 203.0.113.0/24 networks, both routed through the 198.51.100.1 gateway, enter:

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

2. Optionally, verify that the routes were added correctly to the configuration:

   $ nmcli connection show example
   ...
   ipv4.routes:        { ip = 192.0.2.1/24, nh = 198.51.100.1 }
   ...

3. Restart the network connection:

   $ sudo nmcli connection up example

   Warning

   Restarting the connection briefly disrupts connectivity on that interface.

4. Optionally, verify that the route is active:

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

Procedure

1. Open the IPv4 tab.
2. Optionally, disable automatic routes by clicking the On button in the Routes section of the IPv4 tab to use only static routes. If automatic routes are enabled, Red Hat Enterprise Linux uses static routes and routes received from a DHCP server.

3. Enter the address, netmask, gateway, and optionally a metric value:

   

4. Click Apply.

5. Back in the Network window, disable and re-enable the connection by switching the button for the connection to Off and back to On for changes to take effect.

   Warning

   Restarting the connection briefly disrupts connectivity on that interface.

6. Optionally, verify that the route is active:

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

Procedure

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

   $ nm-connection-editor

2. Select the example connection and click the gear wheel icon to edit the existing connection.
3. Open the IPv4 tab.
4. Click the Routes button.

5. Click the Add button and enter the address, netmask, gateway, and optionally a metric value.

   

6. Click OK.
7. Click Save.

8. Restart the network connection for changes to take effect. For example, to restart the example connection using the command line:

   $ sudo nmcli connection up example

9. Optionally, verify that the route is active:

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

Procedure

1. Open the nmcli interactive mode for the example connection:

   $ sudo nmcli connection edit example

2. Add the static route:

   nmcli> set ipv4.routes 192.0.2.0/24 198.51.100.1

3. Optionally, verify that the routes were added correctly to the configuration:

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

   The ip attribute displays the network to route and the nh attribute the gateway (next hop).

4. Save the configuration:

   nmcli> save persistent

5. Restart the network connection:

   nmcli> activate example

   Warning

   When you restart the connection, all connections currently using this connection will be temporarily interrupted.

6. Leave the nmcli interactive mode:

   nmcli> quit

7. Optionally, verify that the route is active:

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

Procedure

1. Create a YAML file, for example ~/add-static-route-to-enp1s0.yml, with the following contents:

   ---
   routes:
     config:
     - destination: 192.0.2.0/24
       next-hop-address: 198.51.100.1
       next-hop-interface: enp1s0

2. Apply the settings to the system:

   # nmstatectl apply ~/add-static-route-to-enp1s0.yml

Procedure

1. If the host on which you want to execute the instructions in the playbook is not yet inventoried, add the IP or name of this host to the /etc/ansible/hosts Ansible inventory file:

   node.example.com

2. Create the ~/add-static-routes.yml playbook with the following content:

   ---
   - name: Configure an Ethernet connection with static IP and additional routes
     hosts: node.example.com
     become: true
     tasks:
     - include_role:
         name: rhel-system-roles.network
   
       vars:
         network_connections:
           - name: enp7s0
             type: ethernet
             autoconnect: yes
             ip:
               address:
                 - 198.51.100.20/24
                 - 2001:db8:1::1/64
               gateway4: 198.51.100.254
               gateway6: 2001:db8:1::fffe
               dns:
                 - 198.51.100.200
                 - 2001:db8:1::ffbb
               dns_search:
                 - example.com
               route:
                 - network: 192.0.2.0
                   prefix: 24
                   gateway: 198.51.100.1
                 - network: 203.0.113.0
                   prefix: 24
                   gateway: 198.51.100.2
             state: up

3. Run the playbook:

   • To connect as root user to the managed host, enter:

     # ansible-playbook -u root ~/add-static-routes.yml

   • To connect as a user to the managed host, enter:

     # ansible-playbook -u user_name --ask-become-pass ~/add-static-routes.yml

     The --ask-become-pass option makes sure that the ansible-playbook command prompts for the sudo password of the user defined in the -u user_name option.

   If you do not specify the -u user_name option, ansible-playbook connects to the managed host as the user that is currently logged in to the control node.

Procedure

1. Add the static IPv4 route to the /etc/sysconfig/network-scripts/route-enp0s1 file:

   ADDRESS0=192.0.2.0
   NETMASK0=255.255.255.0
   GATEWAY0=198.51.100.1

   • The ADDRESS0 variable defines the network of the first routing entry.
   • The NETMASK0 variable defines the netmask of the first routing entry.

   • The GATEWAY0 variable defines the IP address of the gateway to the remote network or host for the first routing entry.

     If you add multiple static routes, increase the number in the variable names. Note that the variables for each route must be numbered sequentially. For example, ADDRESS0, ADDRESS1, ADDRESS3, and so on.

2. Restart the network:

   # systemctl restart network

Procedure

1. Add the static IPv4 route to the /etc/sysconfig/network-scripts/route-enp0s1 file:

   192.0.2.0/24 via 198.51.100.1 dev enp0s1

2. Add the static IPv6 route to the /etc/sysconfig/network-scripts/route6-enp0s1 file:

   2001:db8:1::/64 via 2001:db8:2::1 dev enp0s1

3. Restart the network:

   # systemctl restart network