Configuring a second network interface

Last Updated : Jun 10, 2026 |

About this task

You can add a second network interface by editing your virtual machine settings. Then you can configure this interface using RHEL CLI commands.

In a cluster deployment, perform this procedure on all nodes in the cluster.

Before you begin

  • Prepare the following data for the second network interface:

    • IP address. In a cluster deployment, you must use a unique IP address for each node.

    • Network mask

    • Gateway address

  • Enable EASG functionality. This is required to obtain the sroot user privileges, which are required to perform this procedure.

Procedure

  1. Log in to Avaya Aura® Web Gateway using an SSH connection an administrator.
  2. To obtain the sroot user privileges, run the following command:
    su - sroot
  3. Run the ip address show command to ensure that you have only one network interface.

    For example:

    [admin@aawg ~]$ ip address show
    1: lo:  <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet 127.0.0.1/8 scope host lo
           valid_lft forever preferred_lft forever
        inet6 ::1/128 scope host
           valid_lft forever preferred_lft forever
    2: eth0:  <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
        link/ether 00:0C:29:a8:86:79 brd ff:ff:ff:ff:ff:ff
        inet 192.0.2.26/24 brd 192.0.2.255 scope global eth0
           valid_lft forever preferred_lft forever
        inet6 2001:db8::fea8:8679/64 scope link
           valid_lft forever preferred_lft forever

    In this example, lo is the loopback interface and eth0 is the only network interface.

  4. Do the following to enable Avaya Aura® Web Gateway to process packets from any network:
    1. Open the /etc/sysctl.conf file in a text editor.

      For example: vi /etc/sysctl.conf

    2. Find the net.ipv4.conf.all.rp_filter parameter and change its value to 2.
      net.ipv4.conf.all.rp_filter = 2
    3. Save the file.
    4. Run the reboot command to restart Avaya Aura® Web Gateway.
    5. Run the following command to verify the updated configuration:

      sysctl -a 2>/dev/null | grep "\.rp_filter"

      The following is an example of the command output:

      [admin@aawg ~]$ sysctl -a 2>/dev/null | grep "\.rp_filter"
      net.ipv4.conf.all.rp_filter = 2
      net.ipv4.conf.default.rp_filter = 1
      net.ipv4.conf.eth0.rp_filter = 1
      net.ipv4.conf.lo.rp_filter = 0
  5. On the VMware virtual machine where Avaya Aura® Web Gateway is deployed, add a new network interface.

    For information about adding network interfaces on VMware, see the documentation for the VMware version you used to deploy Avaya Aura® Web Gateway.

  6. Run the ip address show command to ensure that you added a second network interface.

    For example:

    [admin@aawg ~]$ ip address show
    1: lo:  <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet 127.0.0.1/8 scope host lo
           valid_lft forever preferred_lft forever
        inet6 ::1/128 scope host
           valid_lft forever preferred_lft forever
    2: eth0:  <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
        link/ether 00:0C:29:a8:86:79 brd ff:ff:ff:ff:ff:ff
        inet 192.0.2.26/24 brd 192.0.2.255 scope global eth0
           valid_lft forever preferred_lft forever
        inet6 2001:db8::fea8:8679/64 scope link
           valid_lft forever preferred_lft forever
    3: eth1:  <BROADCAST,MULTICAST> mtu 1500 noop state DOWN qlen 1000
        link/ether 00:0C:29:a8:86:80 brd ff:ff:ff:ff:ff:ff
    

    In this example, eth0 is the existing network interface and eth1 is the second network interface you added in the previous step.

  7. Run the following command to copy the configuration file for the second network interface from the configuration file for the existing network interface:

    cp /etc/sysconfig/network-scipts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth1

    The following is an example of the configuration file for the existing network interface:

    [admin@aawg ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth0
    DEVICE=eth0
    BOOTPRO=static
    ONBOOT=yes
    TYPE=Ethernet
    IPADDR=192.0.2.26
    NETMASK=255.255.255.0
    GATEWAY=192.0.2.1
    
  8. Open the /etc/sysconfig/network-scripts/ifcfg-eth1 configuration file for the second network interface in a text editor.

    For example: vi /etc/sysconfig/network-scripts/ifcfg-eht1

  9. Modify the following parameters:
    1. DEVICE: Enter eth1.
    2. IPADDR: Enter the IP address of the second network interface.
    3. NETMASK: Enter the subnetwork mask of the second network interface IP address.
    4. GATEWAY: Enter the gateway address.

    The following is an example of the updated configuration file for the second network interface:

    [admin@aawg ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth1
    DEVICE=eth1
    BOOTPRO=static
    ONBOOT=yes
    TYPE=Ethernet
    IPADDR=198.51.100.29
    NETMASK=255.255.255.0
    GATEWAY=198.51.100.1
    
  10. Save the file.
  11. Run the sudo systemctl restart NetworkManager command to apply changes.
  12. Run the ip address show command to verify that the second network interface is configured.

    For example:

    [admin@aawg ~]$ ip address show
    1: lo:  <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet 127.0.0.1/8 scope host lo
           valid_lft forever preferred_lft forever
        inet6 ::1/128 scope host
           valid_lft forever preferred_lft forever
    2: eth0:  <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
        link/ether 00:0C:29:a8:86:79 brd ff:ff:ff:ff:ff:ff
        inet 192.0.2.26/24 brd 192.0.2.255 scope global eth0
           valid_lft forever preferred_lft forever
        inet6 2001:db8::fea8:8679/64 scope link
           valid_lft forever preferred_lft forever
    3: eth1:  <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
        link/ether 00:0C:29:a8:86:80 brd ff:ff:ff:ff:ff:ff
        inet 198.51.100.29/24 brd 198.51.100.255 scope global eth0
           valid_lft forever preferred_lft forever
        inet6 2001:db8::fea8:8680/64 scope link
           valid_lft forever preferred_lft forever
    
  13. From another computer, run the ping command to ensure that both network interfaces are accessible:

    ping <FIRST NETWORK INETRFACE IP ADDRESS>

    ping <SECOND NETWORK INTERFACE IP ADDRESS>

    For example:

    ping 192.0.2.26
    ping 198.51.100.29