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

TCPDump Test/Tool #115

Open
mfeit-internet2 opened this issue Sep 5, 2016 · 2 comments
Open

TCPDump Test/Tool #115

mfeit-internet2 opened this issue Sep 5, 2016 · 2 comments

Comments

@mfeit-internet2
Copy link
Member

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.

@mfeit-internet2 mfeit-internet2 added this to the 1.1 milestone Sep 5, 2016
@arlake228 arlake228 removed this from the 1.1 milestone May 8, 2017
@bltierney
Copy link
Contributor

bltierney commented Jun 8, 2017

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".

@mfeit-internet2
Copy link
Member Author

mfeit-internet2 commented Jun 27, 2017

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.

Sample command line:

tshark -a duration:15 -c 1 -w /tmp/pcap -q -n

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

No branches or pull requests

6 participants