We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Consider a test that runs tcpdump for a time and spews out the results.
tcpdump
Note that this could produce very large data; consider how to mitigate that.
The text was updated successfully, but these errors were encountered:
this could also run tcptrace automatically, which would reduce the size of the output to send back to the client.
One way to do this would be:
pscheduler task --pcapture tcptrace -option -Sl throughput --dest hostname
This would run tcpdump in parallel with iperf3, and send the results thru tcptrace with the flags "-Sl".
Sorry, something went wrong.
It might be better to use tshark (see https://www.wireshark.org/docs/wsug_html_chunked/AppToolstshark.html) to do the capture. It has a switch to tell it to shut down after a specified number of seconds: -a duration:1234.
tshark
-a duration:1234
Sample command line:
tshark -a duration:15 -c 1 -w /tmp/pcap -q -n
epcjr
No branches or pull requests
Consider a test that runs
tcpdump
for a time and spews out the results.Note that this could produce very large data; consider how to mitigate that.
The text was updated successfully, but these errors were encountered: