User Manual

TRex 22 / 113
cps : 10.0
v
2
ipg : 50000
v
3
rtt : 50000
w : 1
v
1
Duration is 1 second.
v
2
CPS is 10.0.
v
3
IPG is 50 msec.
Running this produces the following output:
[bash]>./bp-sim-32-debug -f cap2/dns_test.yaml -o my.erf -v 3
Table 4.2: Formated results
pkt time sec template fid flow-
pkt-id
client_ip client_port server_ip desc
1 0.010000 0 1 1 16.0.0.1 1024 48.0.0.1 →
2 0.060000 0 1 2 16.0.0.1 1024 48.0.0.1 ←
3 0.210000 0 2 1 16.0.0.2 1024 48.0.0.2 →
4 0.260000 0 2 2 16.0.0.2 1024 48.0.0.2 ←
5 0.310000 0 3 1 16.0.0.3 1024 48.0.0.3 →
6 0.360000 0 3 2 16.0.0.3 1024 48.0.0.3 ←
7 0.410000 0 4 1 16.0.0.4 1024 48.0.0.4 →
8 0.460000 0 4 2 16.0.0.4 1024 48.0.0.4 ←
9 0.510000 0 5 1 16.0.0.5 1024 48.0.0.5 →
10 0.560000 0 5 2 16.0.0.5 1024 48.0.0.5 ←
11 0.610000 0 6 1 16.0.0.6 1024 48.0.0.6 →
12 0.660000 0 6 2 16.0.0.6 1024 48.0.0.6 ←
13 0.710000 0 7 1 16.0.0.7 1024 48.0.0.7 →
14 0.760000 0 7 2 16.0.0.7 1024 48.0.0.7 ←
15 0.810000 0 8 1 16.0.0.8 1024 48.0.0.8 →
16 0.860000 0 8 2 16.0.0.8 1024 48.0.0.8 ←
17 0.910000 0 9 1 16.0.0.9 1024 48.0.0.9 →
18 0.960000 0 9 2 16.0.0.9 1024 48.0.0.9 ←
19 1.010000 0 a 1 16.0.0.10 1024 48.0.0.10 →
20 1.060000 0 a 2 16.0.0.10 1024 48.0.0.10 ←
Use the following to display the output as a chart, with: x axis: time (seconds) y axis: flow ID The output indicates that there are
10 flows in 1 second, as expected, and the IPG is 50 msec
Note
Note the gap in the second flow generation. This is an expected schedular artifact and does not have an effect.
4.2 DNS, take flow IPG from pcap file
In the following example the IPG is taken from the IPG itself.