User Manual

TRex 38 / 113
v
1
Connected to TRex port 0 (client side)
v
2
Connected to TRex port 1 (server side)
v
3
Connected to TRex port 2 (client side)
v
4
Connected to TRex port 3(server side)
One server:
To support a template with one server, you can add “server_addr” keyword. Each port pair will be get different
server IP (According to the “dual_port_mask” offset).
- name: cap2/dns.pcap
cps : 1.0
ipg : 10000
rtt : 10000
w : 1
server_addr : "48.0.0.1"
v
1
one_app_server : true
v
2
wlength : 1
v
1
Server IP.
v
2
Enable one server mode.
In TRex server, you will see the following statistics.
Active-flows : 19509 Clients : 504 Socket-util : 0.0670 %
Open-flows : 247395 Servers : 65408 Socket : 21277 Socket/Clients ←-
: 42.2
Note
• No backward compatibility with the old generator YAML format.
• When using -p option, TRex will not comply with the static route rules. Server-side traffic may be sent from the client side
(port 0) and vice-versa. If you use the -p option, you must configure policy based routing to pass all traffic from router port 1
to router port 2, and vice versa.
• VLAN [?] feature does not comply with static route rules. If you use it, you also need policy based routing rules to pass
packets from VLAN0 to VLAN1 and vice versa.
• Limitation: When using template with plugins (bundles), the number of servers must be higher than the number of clients.
4.11.1 More Details about IP allocations
Each time a new flow is created, TRex allocates new Client IP/port and Server IP. This 3-tuple should be distinct among active
flows.
Currently, only sequential distribution is supported in IP allocation. This means the IP address is increased by one for each flow.
For example, if we have a pool of two IP addresses: 16.0.0.1 and 16.0.0.2, the allocation of client src/port pairs will be
16.0.0.0.1 [1024]
16.0.0.0.2 [1024]
16.0.0.0.1 [1025]
16.0.0.0.2 [1025]
16.0.0.0.1 [1026]
16.0.0.0.2 [1026]
...