User Manual

TRex 50 / 113
responder :
vlan : 200
next_hop : 2.2.2.1
src_ip : 2.2.2.100
count : 4
In this case, TRex attempts to resolve the following addresses using ARP:
1.1.1.1, 1.1.1.2, 1.1.1.3, 1.1.1.4 (and the range 2.2.2.1-2.2.2.4)
If not all IPs are resolved, TRex exits with an error message.
src_ip is used to send gratuitous ARP, and for filling relevant fields in ARP request. If no src_ip is given, TRex looks for
the source IP in the relevant port section in the platform configuration file (/etc/trex_cfg.yaml). If none is found, TRex exits with
an error message.
If a client config file is given, TRex ignores the dest_mac and default_gw parameters from the platform configuration file.
Now, streams will look like:
Initiator side (packets with source in 16.x.x.x net):
• 16.0.0.1 → 48.x.x.x - dst_mac: MAC of 1.1.1.1 vlan: 100
• 16.0.0.2 → 48.x.x.x - dst_mac: MAC of 1.1.1.2 vlan: 100
• 16.0.0.3 → 48.x.x.x - dst_mac: MAC of 1.1.1.3 vlan: 100
• 16.0.0.4 → 48.x.x.x - dst_mac: MAC of 1.1.1.4 vlan: 100
• 16.0.0.5 → 48.x.x.x - dst_mac: MAC of 1.1.1.1 vlan: 100
• 16.0.0.6 → 48.x.x.x - dst_mac: MAC of 1.1.1.2 vlan: 100
Responder side (packets with source in 48.x.x.x net):
• 48.x.x.x → 16.0.0.1 - dst_mac: MAC of 2.2.2.1 , vlan:200
• 48.x.x.x → 16.0.0.2 - dst_mac: MAC of 2.2.2.2 , vlan:200
Note
It is important to understand that the IP to MAC coupling (with either MAC-based or IP-based configuration) is done at the
beginning and never changes. For example, in a MAC-based configuration:
• Packets with source IP 16.0.0.2 will always have VLAN 100 and dst MAC 00:00:00:01:00:01.
• Packets with destination IP 16.0.0.2 will always have VLAN 200 and dst MAC 00:00:00:02:00:01.
Consequently, you can predict exactly which packet (and how many packets) will go to each DUT.
Usage:
[bash]>sudo ./t-rex-64 -f cap2/dns.yaml --client_cfg my_cfg.yaml