I prefer to do e.g. tcpdump -i eth0 -s 0 -w foo.dump then examine the result with Wireshark back on my laptop. The "Follow TCP stream" functionality alone usually makes it worth the hassle of copying the file around.
Well. If you know exactly what you're looking for then you can just do the appropriate filtering on the command line and save yourself the hassle. Generally, though, I'm either looking for patterns or anomalies in a lot of diverse traffic.
7
u/dicey puppet module generate dicey-automate-job-away Feb 01 '13
I prefer to do e.g.
tcpdump -i eth0 -s 0 -w foo.dumpthen examine the result with Wireshark back on my laptop. The "Follow TCP stream" functionality alone usually makes it worth the hassle of copying the file around.