[Tcpreplay-users] Replaying small dumps at high speed

[Lothar B. <ma...@lo...>]

Hi,

i replayed a small dump file (about 30 packets) using -l 10000 at different=
=20
speeds (2000, 4000, 8000 and 15000 pkts/s) using tcpreplay 2.x and tcprepla=
y=20
3.0.betax
Both, tcpreplay 2 and 3, displayed the message

processing file: /home/lothar/net/localhost.dump

on stdout.

Tcpreplay 2 writes this message once, while tcpreplay 3.0 writes the messag=
e=20
each time the dumpfile is processed. This behavior results in an huge amoun=
t=20
of messages printed to the screen with tcpreplay.
The more packets per second you replay, the more busy tcpreplay gets printi=
ng=20
these messages.

Whereas tcpreplay 2 had no problem to send out all packets at 15000 pkts/s,=
=20
tcpreplay 3 already got problems at 4000 pkts/s because it was so busy=20
printing its messages.

I think it would be a good idea to get the tcpreplay-2 behavior back. Is th=
at=20
possible for the next beta or the final release?

Best regards,
  Lothar

=2D-
Blog: http://const-cast.blogspot.com