| 1 |
Misc info |
| 2 |
========= |
| 3 |
|
| 4 |
Running tests with the D-ITG tool |
| 5 |
--------------------------------- |
| 6 |
|
| 7 |
This version of flent has experimental support for running and parsing the |
| 8 |
output of the D-ITG test tool (see |
| 9 |
http://traffic.comics.unina.it/software/ITG/). Flent supports parsing the |
| 10 |
one-way delay as measured by D-ITG. However, in order to do so, the data needs |
| 11 |
to be collected at the receiver end, statistics extracted, and the result passed |
| 12 |
back to flent on the sending side. |
| 13 |
|
| 14 |
To perform this function, flent supports a control server which will listen to |
| 15 |
XML-RPC requests, spawn an appropriate ITGRecv instance and, after the test is |
| 16 |
done, parse its output and make it available for flent to retrieve. This control |
| 17 |
server is available as a Python file that by default is installed in |
| 18 |
:file:`/usr/share/doc/flent/misc`. It currently requires a patched version of |
| 19 |
D-ITG v2.8.1. The patch is also included in the same directory. |
| 20 |
|
| 21 |
Note that the D-ITG server is finicky and not designed with security in mind. |
| 22 |
For this reason, the control server includes HMAC authentication to only allow |
| 23 |
authenticated clients to run a test against the server; however there is |
| 24 |
currently no support for enforcement of this in e.g. firewall rules. Please bear |
| 25 |
this in mind when running a publicly reachable ITGRecv instance (with or without |
| 26 |
the control server). Another security issue with the control server is that the |
| 27 |
Python XML-RPC library by default is vulnerable to XML entity expansion attacks. |
| 28 |
For this reason, it is highly recommended to install the :py:mod:`defusedxml` |
| 29 |
library (available at https://pypi.python.org/pypi/defusedxml/) on the host |
| 30 |
running the control server. The server will try to find the library on startup |
| 31 |
and refuse to run if it is not available, unless explicitly told otherwise. |
| 32 |
|
| 33 |
Due to the hassle of using D-ITG, it is recommended to install :command:`irtt` |
| 34 |
instead and use that for VoIP tests. |
| 35 |
|
| 36 |
Bugs |
| 37 |
---- |
| 38 |
|
| 39 |
Under some conditions (such as severe bufferbloat), the UDP RTT measurements |
| 40 |
done by netperf can experience packet loss to the extent that the test aborts |
| 41 |
completely, which can cause missing data points for some measurement series. |
| 42 |
The --socket-timeout feature can alleviate this, but requires a recent SVN |
| 43 |
version of netperf to work. Flent tries to detect if netperf supports this |
| 44 |
option and enables it for the UDP measurements if it does. Using :command:`irtt` |
| 45 |
for UDP measurements is a way to alleviate this; Flent will automatically detect |
| 46 |
the availability of irtt and use it if available. |
| 47 |
|
| 48 |
Probably many other bugs. Please report any found to |
| 49 |
https://github.com/tohojo/flent/issues and include the output of :option:`flent |
| 50 |
--version<-V>` in the report. A debug log (as obtained with :option:`flent |
| 51 |
--log-file<-L>`) is also often useful. |