User Manual

TRex 33 / 113
4.10 Mimicking stateless traffic under stateful mode
Note
TRex supports also true stateless traffic generation. If you are looking for stateless traffic, please visit the following link: TRex
Stateless Support [?]
With this feature you can "repeat" flows and create stateless, IXIA like streams. After injecting the number of flows defined by
limit, TRex repeats the same flows. If all templates have limit the CPS will be zero after some time as there are no new
flows after the first iteration.
IMIX support:
Example:
[bash]>sudo ./t-rex-64 -f cap2/imix_64.yaml -d 1000 -m 40000 -c 4 -p
Warning
The -p is used here to send the client side packets from both interfaces. (Normally it is sent from client ports only.) With
this option, the port is selected by the client IP. All the packets of a flow are sent from the same interface. This may
create an issue with routing, as the client’s IP will be sent from the server interface. PBR router configuration solves
this issue but cannot be used in all cases. So use this -p option carefully.
imix_64.yaml
cap_info :
- name: cap2/udp_64B.pcap
cps : 1000.0
ipg : 10000
rtt : 10000
w : 1
limit : 1000
v
1
v
1
Repeats the flows in a loop, generating 1000 flows from this type. In this example, udp_64B includes only one packet.
The cap file "cap2/udp_64B.pcap" includes only one packet of 64B. This configuration file creates 1000 flows that will be
repeated as follows: f1 , f2 , f3 . . . . f1000 , f1 , f2 . . . where the PPS == CPS for -m=1. In this case it will have PPS=1000 in sec
for -m==1. It is possible to mix stateless templates and stateful templates.
Imix YAML cap2/imix_fast_1g.yaml example
- duration : 3
generator :
distribution : "seq"
clients_start : "16.0.0.1"
clients_end : "16.0.0.255"
servers_start : "48.0.0.1"
servers_end : "48.0.255.255"
clients_per_gb : 201
min_clients : 101
dual_port_mask : "1.0.0.0"
tcp_aging : 0
udp_aging : 0
mac : [0x0,0x0,0x0,0x1,0x0,0x00]
cap_info :
- name: cap2/udp_64B.pcap