Traffic Generator

Enable Javascript to display Table of Contents.

mz (Mausezahn)

Positive: Can generate more traffic than any other traffic generator
Negative: Does not check whether traffic was lost

sudo mz -B DESTINATION_IP -t udp -p PACKETSIZE -d DELAY_BETWEEN_TRANSMISSIONS_IN_US -c PACKET_CNT

Delay can also be specified as "100m" for 100 milli seconds or "100s" for 100 seconds

$ sudo mz -B 10.0.0.4 -t udp "sp=12300, dp=12400" -p 550 -d 10u -c 1000000

Mausezahn will send 1000000 frames... 2.22 seconds (451010 packets per second)

$

After -t udp the source port and destination port can be specified.

iperf

Positive: Easy to setup
Negative: Too slow for small packet sizes (currently with skiptest3 and host137 it only works from 350byte packets)
Negative: Sends more packets as shown (e.g. says 150001 packets but according to wireshark 150071 are sent)
Negative: When sending from iperf 2.0.9 to iperf 2.0.5 with 120m, it works fine when the time is less or equal 4294 seconds. When it's 4295 seconds it transfers only 77.2 Mbits/sec.

Client

sudo iperf -c DESTINATION_IP -p PORT -u -b DATARATE -l PACKETSIZE -t TIME_IN_SECONDS

The datarate can be specified like "72,7m".

Server

iperf -s -u -U -l PACKETSIZE -p PORT -i REPORT_INTERVAL_IN_SECONDS

Client IPv6

sudo iperf -V -c fe80::2e0:33ff:fe05:cebc%eth_internal -p 11000 -u -b 10M -l 120 -t 120

IPv6 needs the '-V' flag and an network interface specified after the IP address, separated by the '%' letter.

Server IPv6

iperf -s -V -u -U -l 120 -p 11000 -i 1

On the server also the '-V' flag has to be specified for IPv6.

Jperf

Graphical user interface for iperf.

There are different repositories to get jperf:

Github from Andy Grove/AgilData(=CodeFutures) (up to version 2.0)
Google Code (up to version 2.0.2, discontinued)
Sourceforge as part of iperf repository

See download page.

ITGSend / ITGRecv

Positive: High performance when using shared memory on receiver side
Negative: Hard to get results

On the one side, we have to start ITGSend with the specified parameters:

ITGSend -a DESTINATION_IP -T UDP -c PACKETSIZE -C PACKETS_PER_SECOND -t TIME_IN_MS -poll

On the other side (DESTINATION_IP) we have to start ITGRecv.

ITGRecv -l /dev/shm/itgrecv_kkr.log

When the recording is done, we can use ITGDec to create a statistic:

ITGDec /dev/shm/itgrecv_kkr.log

With the parameter -p we can figure out, where the drops appeared:

ITGDec /dev/shm/itgrecv_kkr.log -p 10000

The result of ITGDec is always saved to file packetlogs.dat

cat packetlogs.dat