Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Max replay rate for all loops except first when omitting --mbps option #85

Closed
abiryukov opened this issue Jun 17, 2014 · 2 comments
Closed
Assignees
Milestone

Comments

@abiryukov
Copy link

  1. run: tcpreplay -i eth6 --loop=3 bigFlows.pcap
Expected

this capture file has original rate ~10Mbps and duration ~300s. With 3 loops it should produce ~900s of replay at ~10Mbps

Actual

first loop is done at the file's original rate. All loops after that - at max rate

Actual: 2374845 packets (1066253352 bytes) sent in 302.08 seconds.
Rated: 3520663.3 Bps, 28.16 Mbps, 7841.50 pps
Flows: 40686 flows, 134.34 fps, 7120611 flow packets, 3924 non-flow
@fklassen fklassen added this to the 4.0.5 milestone Jun 17, 2014
@fklassen fklassen self-assigned this Jun 17, 2014
@fklassen fklassen added 4.0.5 and removed 4.0.4 labels Jun 17, 2014
@abiryukov
Copy link
Author

could be related: when running command as above, allowing error output (without 2> /dev/null), there is a warning for every packet in all loops after first:

Warning: Packet #1 has gone back in time!
Warning: Packet #2 has gone back in time!
Warning: Packet #3 has gone back in time!

@fklassen
Copy link
Member

Thanks Alex. Sounds similar to a fix I did for #75

Either I broke something, or a similar fix needs to be applied to the time for every loop pass.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants