User Manual

TRex 26 / 113
Table 4.5: (continued)
pkt time sec fid flow-
pkt-id
client_ip client_port server_ip desc
10 5.030944 5 2 16.0.0.1 1028 48.0.0.5 ←
11 6.010000 6 1 16.0.0.1 1029 48.0.0.6 →
12 6.030944 6 2 16.0.0.1 1029 48.0.0.6 ←
13 7.010000 7 1 16.0.0.1 1030 48.0.0.7 →
14 7.030944 7 2 16.0.0.1 1030 48.0.0.7 ←
15 8.010000 8 1 16.0.0.1 1031 48.0.0.8 →
16 8.030944 8 2 16.0.0.1 1031 48.0.0.8 ←
17 9.010000 9 1 16.0.0.1 1032 48.0.0.9 →
18 9.030944 9 2 16.0.0.1 1032 48.0.0.9 ←
19 10.010000 a 1 16.0.0.1 1033 48.0.0.10 →
20 10.030944 a 2 16.0.0.1 1033 48.0.0.10 ←
In this case there is only one client so only ports are used to distinc the flows you need to be sure that you have enogth free
sockets when running TRex in high rates
Active-flows : 0 Clients : 1
v
1
Socket-util : 0.0000 %
v
2
Open-flows : 1 Servers : 254 Socket : 1 Socket/Clients : 0.0
drop-rate : 0.00 bps
v
1
Number of clients
v
2
sockets utilization (should be lowwer than 20%, elarge the number of clients in case of an issue).
4.5 DNS, W=1
w is a tunable to the IP clients/servers generator. w=1 is the default behavior. Setting w=2 configures a burst of two allocations
from the same client. See the following example.
- duration : 10.0
generator :
distribution : "seq"
clients_start : "16.0.0.1"
clients_end : "16.0.0.10"
servers_start : "48.0.0.1"
servers_end : "48.0.0.3"
clients_per_gb : 201
min_clients : 101
dual_port_mask : "1.0.0.0"
tcp_aging : 1
udp_aging : 1
mac : [0x00,0x00,0x00,0x01,0x00,0x00]
cap_ipg : true
#cap_ipg_min : 30
#cap_override_ipg : 200
cap_info :
- name: cap2/dns.pcap
cps : 1.0
ipg : 10000
rtt : 10000
w : 2
v
1