AWS EC2 multiple interface network configuration

[Mayank Mhatre]

Hi all,

For Trex in AWS EC2, since it is mandatory to have multiple interfaces (eth1 and eth2 in addition to eth0), what are all necessary linux settings that are need to be done after attaching extra interfaces the instance.

I have done following changes after  network interface attachment in AWS console,

1. [centos@ip-10-123-75-111 ~]$ cat /etc/sysconfig/network
NOZEROCONF=yes
GATEWAYDEV=eth0 # this is done to avoid asymmetric routing issues and my traffic will leave the instance only via eth0
# Created by cloud-init on instance boot automatically, do not edit.
#
NETWORKING=yes

2. [centos@ip-10-123-75-111 ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth1
DEVICE="eth1"
BOOTPROTO=none
ONBOOT="yes"
PREFIX=20
IPADDR=10.123.154.113

3. [centos@ip-10-123-75-111 ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth2
DEVICE="eth2"
BOOTPROTO=none
ONBOOT="yes"
PREFIX=20
IPADDR=10.123.163.56

4. [centos@ip-10-123-75-111 ~]$ cat /etc/sysconfig/network-scripts/route-eth1
default via 10.123.144.1 dev eth1 table 2
10.123.144.0/20 dev eth1 src 10.123.154.113 table 2

5. [centos@ip-10-123-75-111 ~]$ cat /etc/sysconfig/network-scripts/route-eth2
default via 10.123.160.1 dev eth2 table 3
10.123.160.0/20 dev eth2 src 10.123.163.56 table 3

6. [centos@ip-10-123-75-111 ~]$ cat /etc/sysconfig/network-scripts/rule-eth1
from 10.123.154.113/32 table 2

7. [centos@ip-10-123-75-111 ~]$ cat /etc/sysconfig/network-scripts/rule-eth2
from 10.123.163.56/32 table 3

Can anyone let me know whether this routing policies are needed be established or will it cause any problem with trex traffic.

Moreover, with these settings I have 1 Trex instances in the same VPC, server instance of which is not receiving any packets from STL mode.

Thanks,

Mayank