User Manual

TRex 20 / 113
16 ,8.020000,8,0x9054760,2,93,0,0,1,0,0,10000008,30000008,1024
17 ,9.010000,9,0x9055598,1,77,0,1,0,0,0,10000009,30000009,1024
18 ,9.020000,9,0x9054760,2,93,0,0,1,0,0,10000009,30000009,1024
19 ,10.010000,a,0x9055598,1,77,0,1,0,0,0,1000000a,3000000a,1024
20 ,10.020000,a,0x9054760,2,93,0,0,1,0,0,1000000a,3000000a,1024
file stats
=================
m_total_bytes : 1.66 Kbytes
m_total_pkt : 20.00 pkt
m_total_open_flows : 10.00 flows
m_total_pkt : 20
m_total_open_flows : 10
m_total_close_flows : 10
m_total_bytes : 1700
v
1
Global statistics on the templates given. cps=connection per second. tps is template per second. they might be different
in case of plugins where one template includes more than one flow. For example RTP flow in SFR profile (avl/de-
lay_10_rtp_160k_full.pcap)
v
2
Generator output.
[bash]>wireshark my.erf
gives
TRex generated output file images/dns_trex_run.png
As the output file shows. . .
• TRex generates a new flow every 1 sec.
• Client IP values are taken from client IP pool .
• Servers IP values are taken from server IP pool .
• IPG (inter packet gap) values are taken from the configuration file (10 msec).
Note
In basic usage, TRex does not wait for an initiator packet to be received. The response packet will be triggered based only
on timeout (IPG in this example). In advanced scenarios (for example, NAT), The first packet of the flow can process by TRex
software and initiate the response packet only when a packet is received. Consequently, it is necessary to process the template
pcap file offline and ensure that there is enough round-trip delay (RTT) between client and server packets. One approach is to
record the flow with a Pagent that creats RTT (10 msec RTT in the example), recording the traffic at some distance from both
the client and server (not close to either side). This ensures sufficient delay that packets from each side will arrive without delay
in the DUT. TRex-dev will work on an offline tool that will make it even simpler. Another approach is to change the yaml ipg
field to a high enough value (bigger than 10msec ).
Converting the simulator text results in a table similar to the following:
Table 4.1: DNS example formatted results
pkt time sec fid flow-
pkt-id
client_ip client_port server_ip direction
1 0.010000 1 1 16.0.0.1 1024 48.0.0.1 →
2 0.020000 1 2 16.0.0.1 1024 48.0.0.1 ←
3 2.010000 2 1 16.0.0.2 1024 48.0.0.2 →