Hi, i replayed a small dump file (about 30 packets) using -l 10000 at different speeds (2000, 4000, 8000 and 15000 pkts/s) using tcpreplay 2.x and tcpreplay 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 message each time the dumpfile is processed. This behavior results in an huge amount of messages printed to the screen with tcpreplay. The more packets per second you replay, the more busy tcpreplay gets printing these messages. Whereas tcpreplay 2 had no problem to send out all packets at 15000 pkts/s, tcpreplay 3 already got problems at 4000 pkts/s because it was so busy printing its messages. I think it would be a good idea to get the tcpreplay-2 behavior back. Is that possible for the next beta or the final release? Best regards, Lothar -- Blog: http://const-cast.blogspot.com
pgpKwkzKsMteS.pgp
Description: PGP signature
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Tcpreplay-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tcpreplay-users
